On Sun, 06 Aug 2006 06:21:55 +0200, Hisham Muhammad <[EMAIL PROTECTED]>
wrote:
On 8/5/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
Making use of unmanaged files I noticed that, in recipes, one has to
specify the unmanaged files in a variable, unmanaged_files, in the
recipe
instead of a file, Resources/UnmanagedFiles, in the recipe directory. I
think the latter is more natural as it follows the same layout as
packages.
Sounds like a good idea, but on the other hand having them listed in
the text of the recipe makes it easier to inspect it and not forget
about it (I can understand Dependencies being "meta" information
enough to warrant being listed in a separate file but I'm not sure
about this.) What I mean is: I do see your point but I'm undecided
about it. More voices are welcome. :)
Well, one always inspects the Dependencies file before submitting a
recipe/package, right? ;)
Anyhow as UnmanagedFiles is manually created, it's no need to inspect it
as recipe author (because you created it) and if one are to inspect the
recipe as third person one can cat the UnmanagedFiles file. Besides having
it as an file becuase beeing consistant with package layout, you can look
on lukas' recipe on SVGAlib. He has 10 files as unmanaged, which is a bit
much, imo, to have listed as a variable.
Just came to think about recipes made with NewVersion, if the file list
changes. How about adding a suffix to the UnmanagedFiles file and if that
suffix exists one gets a warning when one compiles and the files installed
out of sandbox differs from the files listed in UnmanagedFiles, so that
one can check the file list for newly created recipes. If the list in
UnmanagedFiles is correct the suffix should be removed.
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
