All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Misc patches for grub2
Date: Tue, 5 Aug 2008 10:30:11 -0700	[thread overview]
Message-ID: <20080805103011.02a22a74@gibibit.com> (raw)
In-Reply-To: <ca0f59980808050714r239985a4x47ec91c2fd7f965b@mail.gmail.com>

On Tue, 5 Aug 2008 22:14:37 +0800
Bean <bean123ch@gmail.com> wrote:

> On Tue, Aug 5, 2008 at 6:36 PM, Marco Gerards <mgerards@xs4all.nl>
> wrote:
> > For some reason I have some doubts about lib/.  But I do not have a
> > better name in mind either.  What does belong in there?  Do you
> > happen to have other names in mind as a suggestion? :-)
> 
> The files in this directory are used by both modules and utilities,
> while files in util/ are only used by utilities.
> 
> I also sense that lib is a little strange, but I can't think of a
> better name. Some alternative name could be: shared, common, helper.

Until recently, it looked like only the LZMA code was in 'lib/'.  This
led me to think along the following lines:  Since the lzma code is in
lib, which is essentially just a modified import of the LZMA SDK 4.58
beta, I thought that lib's intent was something like:

  Code imported from other projects.
  Although this code may have been modified from its upstream form to
  work for GRUB, it is still, in essence, a library that is maintained
  separately from GRUB, and we should be able to stay in sync with the
  upstream project by integrating new versions when we want to.

By keeping imported code as close to its original form as possible
(and in a logical, self contained source tree location such as
'lib/lzma/'), it will make it much easier to upgrade that imported
code to a new version of the upstream.  Perhaps when LZMA SDK 4.58
final is released they will have fixed a bug or two... then it's easy
to bring that forward if we haven't changed the code too much in GRUB.

Just a thought on what 'lib/' *could* be...

Regards,
Colin



  reply	other threads:[~2008-08-05 17:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 16:38 [PATCH] Misc patches for grub2 Bean
2008-07-25 17:19 ` Chris Knadle
2008-07-25 17:45   ` Bean
2008-07-25 18:58     ` Chris Knadle
2008-07-27  4:36       ` Pavel Roskin
2008-07-25 20:53 ` Robert Millan
2008-07-26  4:28   ` Bean
2008-07-27  4:55     ` Pavel Roskin
2008-07-27  6:00       ` Bean
2008-07-27  7:05         ` Pavel Roskin
2008-07-27  7:14           ` Bean
2008-07-27  7:20             ` Pavel Roskin
2008-07-27  7:30               ` Bean
2008-07-27  7:33                 ` Pavel Roskin
2008-07-27 13:51                   ` Bean
2008-08-05 10:36 ` Marco Gerards
2008-08-05 14:14   ` Bean
2008-08-05 17:30     ` Colin D Bennett [this message]
2008-08-05 20:11   ` 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=20080805103011.02a22a74@gibibit.com \
    --to=colin@gibibit.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.