David Douthitt, 2001-03-30 09:50 -0600
>...what you have after this is done is a source code directory that
>could, in theory, be compiled straight away to create a usable LRP
>binary.
David,
That sounds great!
> > >* I never created *.diff files for makefile only changes - such as
> > >static libraries, and gcc options like -O2 -s -g
>
>This means that the patches to the source code are incomplete. It
>also means that some binaries would be created without the appropriate
>libraries built-in, and people would begin asking about missing
>libraries.
This doesn't sound good.
> > >* I almost never added -s, leaving that to a "strip" done later.
>
>This means that the binaries will be unnecessarily large; tftp went
>from 80k to 22k once a "strip" was done.
>
>In short, what I want to be able to do is give one the tar.gz file
>(unmodified) and a diff file, and with the appropriate patch, create a
>new binary.
Ok, I just added wrappers for .o and .tar.gz. I can remove them later if
they're not needed. Is there anything else we need to do?
>This also makes me think that there is a need to be able to create an
>*.lrp given the appropriate files and such. Such a script would be
>used in a similar way to configure, but would be able to create the
>files in /var/lib/lrpkg/ on the fly. Presumably, a patch could
>contain these files, and the makefile modified to create the *.lrp in
>the source directory.
This gets back to my original post. I created a binary wrapper for .lrp, so
we could add them to CVS. If there is a clean way to use the source
instead, I'm all for it.
--
Mike Noyes <[EMAIL PROTECTED]>
http://leaf.sourceforge.net/
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
