sm-grimoire AT lists.ibiblio.org
Subject: Discussion of Spells and Grimoire items
List archive
- From: "Ryan Abrams" <ryan.abrams AT attbi.com>
- To: "Andrew Stitt" <afrayedknot AT thefrayedknot.armory.com>
- Cc: <sm-grimoire AT lists.ibiblio.org>
- Subject: Re: [SM-Grimoire]CVS or Perforce
- Date: Tue, 6 Aug 2002 16:22:28 -0500
Andrew,
I know your response is intended in sarcasm, but...
We ARE a distro that aims to be 100% free.. or as close as possible.
Now I don't consider myself to have the right to tell others what to use..
and if people want to use p4, thats fine. But Julian is right that we need
to offer a way for people to be equal if they choose to take the time to
learn the free software version.
Basically, we need to offer our users AND developers the ability to stay
100% free. If that means dropping perforce, ok. But I think a two way sync
would be fine by me. As soon as that is setup, we will script the grimoire
pull from the cvs, which will be the "official" repository (as it looks
better. But that doesnt mean the p4 server can't continue to be used and
synced, if people prefer it.
This whole "best tool" vs "free tool" thing can get emotional. Lets try to
avoid that, and recognize that both sides are right (its purely a value
judgement) - and lets do something that makes it possible for both sides to
work together.
-Ryan
----- Original Message -----
From: "Andrew Stitt" <afrayedknot AT thefrayedknot.armory.com>
To: "Source Mage Grimoire" <sm-grimoire AT lists.ibiblio.org>
Sent: Tuesday, August 06, 2002 4:11 PM
Subject: Re: [SM-Grimoire]CVS or Perforce
> On Tue, Aug 06, 2002 at 10:34:10PM +0200, Julian v. Bock wrote:
> > Hi
> >
> > >>>>> "AS" == Andrew Stitt <afrayedknot AT thefrayedknot.armory.com>
writes:
> >
> > AS> That also gives us
> > AS> a huge advantage towards the p4 vs cvs debate because then each
> > AS> section, according to the official maintainer, can be either p4 or
> > AS> cvs, and anyone wishing to work on that section must use the
> > AS> maintainers choice.
> >
> > Nobody who wants to contribute (help the maintainer; do the work while
> > the maintainer is on vacation; etc.) should be forced to use unfree
> > software (p4).
> >
> <sarcastic response>
> if thats the game you want to play, then no one should be forced to learn
> an overcomplicated SCM system that has way more features then we ever
> need, but still cant delete directories without the admin's permissions,
> which if i need remind anyone is a central part of our grimoire, we arent
> a software program that has a few predifined directories for source code,
> each spell is a seperate directory.
> </sarcastic response>
>
> It also worth noting that i have no qualms (in reality) about what SCM we
> use, fuck perforce if you want to, use something other then cvs or
> perforce if you want, i could care less. Go with some other submission
> process, hell, we can use submit from my universities servers for all
> that matters!
>
> My point is, we can just dispel all this crap about how if
> A works on B's section, but B uses perforce and A uses CVS they wont see
> each other's changes <rant> because trying to maintain the same files
> with two different SCM's at the same time is just fucking stupid!</rant>
> The realistic solution to this is to not try and keep using both cvs and
> p4 on the same stuff at the same time, its just not gonna work.
>
> That said if you REALLY have a problem with using SCM foo because its
> bar then just email the maintainer what you've done, or we can switch
> it over to something else the substitute maintainers are more comfortable
> with while they are on vacation or something.
>
> The way this whole issue is going now is "we need to have just one scm
> because using two on the same project is just fucking stupid", if you get
> stuck in that mindset then either all the perforce people are going to
> get annoyed at having to use cvs, or all the cvs people (like you) are
> going to gripe about having to use perforce, at least this way we get a
> greater amount of freedom, but the grimoire isnt a nightmare to maintain.
>
> unless of course we can find some way of keeping cvs and perforce
> completely in sync with each other, and get past all the differences
> between them and everything else, then by all means, use both, but thats
> not where my money is going right now.
>
> Andrew
>
> _______________________________________________
> SM-Grimoire mailing list
> SM-Grimoire AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-grimoire
-
[SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Julian v. Bock, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Ryan Abrams, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Dufflebunk, 08/06/2002
- Re: [SM-Grimoire]CVS or Perforce, Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Dufflebunk, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Ryan Abrams, 08/06/2002
- Re: [SM-Grimoire]CVS or Perforce, Eric Sandall, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Ryan Abrams, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Julian v. Bock, 08/06/2002
- <Possible follow-up(s)>
-
Re: [SM-Grimoire]CVS or Perforce,
Sergey A. Lipnevich, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Jon Svendsen, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Julian v. Bock, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Sergey A. Lipnevich, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Ryan Abrams, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Sergey A. Lipnevich, 08/05/2002
- Re: [SM-Grimoire]CVS or Perforce, Jason Flatt, 08/06/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Jon Svendsen, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Eric Sandall, 08/05/2002
-
Re: [SM-Grimoire]CVS or Perforce,
Andrew Stitt, 08/06/2002
Archive powered by MHonArc 2.6.24.