eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

223
active users

#perforce

0 posts0 participants0 posts today
I know nothing<p>Today's been one of those days where I wish we were using anything other than <a href="https://mastodon.ie/tags/perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>perforce</span></a> for version control. This thing is broken beyond belief. Working on several changelists? Sure, but don't create new files, shelving them and reverting the changelist doesn't remove the newly added file from the filesystem. Which breaks <a href="https://mastodon.ie/tags/ceedling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ceedling</span></a>'s automatic test discovery. The work around is to rename the test_* file with some other prefix manually. It sucks.<br><a href="https://mastodon.ie/tags/versioncontrol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>versioncontrol</span></a></p>
Alanna 🏳️‍🌈🏳️‍⚧️<p>The next person who advocates that "Perforce is more user friendly than Git and better for artists." to my face will get a custard pie in response. It really isn't any different to any other VCS is terms of complexity and arguing that it is "user friendly" compared to git is just lies.</p><p><a href="https://mastodon.ie/tags/versioncontrol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>versioncontrol</span></a> <a href="https://mastodon.ie/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>git</span></a> <a href="https://mastodon.ie/tags/perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>perforce</span></a> <a href="https://mastodon.ie/tags/software_engineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>software_engineering</span></a></p>
anarcat<p><a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>perforce</span></a> is forking <a href="https://kolektiva.social/tags/puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>puppet</span></a> into a closed source version <a href="https://github.com/OpenPuppetProject/planning/discussions/11" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OpenPuppetProject/p</span><span class="invisible">lanning/discussions/11</span></a></p>
anarcat<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@genebean" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>genebean</span></a></span> they're doing a serious mistake, and everyone is telling them so, but at this point, i don't care about <a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>perforce</span></a> at all, i'm more worried about <a href="https://kolektiva.social/tags/puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>puppet</span></a>. if other projects are any reference, however, this will hurt the community (and destroy the name puppet), but we will prevail</p>
anarcat<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@genebean" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>genebean</span></a></span> <a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>perforce</span></a> has been explicit in asking the community to maintain the opensource version and produce binary packages for <a href="https://kolektiva.social/tags/puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>puppet</span></a>, so we're actually doing what they want, in a sense, maybe not in the way they expect</p>
anarcat<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@genebean" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>genebean</span></a></span> my perspective on this is that we're not forking <a href="https://kolektiva.social/tags/Puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Puppet</span></a>, <a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>perforce</span></a> is forking puppet, and refusing the community the use of their brand name</p>
Troed Sångberg<p>Don't use centralized services for community projects, part 3451.</p><p><a href="https://infosec.exchange/@isotopp/113310756647450391" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">infosec.exchange/@isotopp/1133</span><span class="invisible">10756647450391</span></a></p><p><a href="https://ioc.exchange/tags/Slack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Slack</span></a> <a href="https://ioc.exchange/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Matrix</span></a> <a href="https://ioc.exchange/tags/Puppet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Puppet</span></a> <a href="https://ioc.exchange/tags/Perforce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Perforce</span></a></p>