grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH]: Fix sparc64 build...


From: David Miller
Subject: Re: [PATCH]: Fix sparc64 build...
Date: Fri, 04 Dec 2009 13:34:39 -0800 (PST)

From: Robert Millan <address@hidden>
Date: Fri, 4 Dec 2009 21:58:25 +0100

> On Thu, Dec 03, 2009 at 01:03:09PM -0800, David Miller wrote:
>> 
>> Thanks, but I don't feel comfortable enough with bzr yet.
>> 
>> I had to struggle just to get things checked out, as the bzr
>> package in Debian stable is too old to use to access to repo.
>> 
>> (For the record I disagree with the source control system choosen,
>>  and the fact that a common current Linux distribution doesn't even
>>  provide a version of the tool necessary to access the repo really
>>  convinces me further of that.)
> 
> For a Lenny system the following should do the trick:
> 
>   echo "deb http://backports.org/debian lenny-backports main" | sudo tee -a 
> /etc/apt/sources.list
>   gpg --keyserver pgp.mit.edu --recv-keys 16BA136C
>   gpg --export -a 16BA136C | sudo apt-key add -
>   sudo apt-get update
>   sudo apt-get install -t lenny-backports bzr

That's not a straightforward and low barrier of entry for new
developers who want to simply check out the grub code and start
contributing.  That's my point.

Do you want lots of people involved, or do you want people to have
to jump through hoops and go out of their way to get at your tree?

Heck, for this reason alone, subversion was a better situation.

Mercurial, GIT, or pretty any other distributed source control system
would have worked out of the box with the client versions provided in
debian stable and other distributions.

So, I still believe BZR was a bad choice of a source control system.

And how many times have you guys wrecked your repository already?
:-)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]