From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Experimental branch for GRUB
Date: Fri, 23 Oct 2009 15:45:28 +0200 [thread overview]
Message-ID: <20091023134528.GA7119@thorin> (raw)
In-Reply-To: <ca0f59980910230006x7ae63b7fq5e220f98dccd83ca@mail.gmail.com>
On Fri, Oct 23, 2009 at 03:06:02PM +0800, Bean wrote:
>
> Hi,
>
> I take a quick look at bazaar, it seems to be working fine. However,
> if we are to use bazaar, I suggest we host the project at launchpad,
> for several reasons:
>
> Launchpad have a nice web interface.
>
> Launchpad can build ubuntu package from source code.
>
> Like GITHUB, launchpad allows users to fork the project and work on
> user branch. This is important for big patch as it usually go through
> several few steps before completion.
>
> We might want to create a unified repo for grub and grub-extra. As
> grub doesn't support external module building, split it in two parts
> is not convenient for both developer and user. Therefore, we can
> maintain an unified source tree in the experimental repo, and push
> patch to the corresponding project when applied upstream.
>
> We don't want to mix bug report for experiential feature with official
> grub2. Launchpad has its own bug tracking system, we can use it to
> process bug report concerning the experimental branch.
I've to go soon and can go in more detail later, but user branches work
fine. I put two of my local patchsets there just a few minutes ago,
check http://bzr.savannah.gnu.org/lh/grub/people/robertmh/.
I think building deb from snapshots of this experimental branch is a good
idea, and it can be done in any place you see fit, BUT if a proprietary
solution is used, the GNU project can't endorse those (e.g. we wouldn't
link to them). I haven't followed the latest developments on which parts
of Launchpad have been liberated. In any case, if this turns out to be a
problem I can assist with the deb-building process (I got almost a decade of
experience with it).
GRUB does support external module building, but it's very impractical. This
is why in Debian we opted for integrating grub-extras at source level, which
is also more solid (no need for ABI checks). I intend to make it easier for
external source modules to be integrated into GRUB without need for patching
anything, but I haven't found the time to do this (maybe later this weekend).
As for bug reports, due to the nature of an experimental branch I don't
expect they will be very common. Anyhow, I'll have a look at Savannah
BTS' versioning capabilities.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-10-23 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 9:17 Experimental branch for GRUB Bean
2009-10-22 22:17 ` Robert Millan
2009-10-23 7:06 ` Bean
2009-10-23 13:45 ` Robert Millan [this message]
2009-10-23 14:08 ` Colin Watson
2009-10-24 12:45 ` Robert Millan
2009-10-23 14:44 ` Vladimir 'phcoder' Serbinenko
2009-10-23 14:35 ` Vladimir 'phcoder' Serbinenko
2009-10-24 13:09 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091023134528.GA7119@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.