On Tue, 5 Aug 2008 22:14:37 +0800 Bean <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 6:36 PM, Marco Gerards <[EMAIL PROTECTED]> > 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 _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
