Mike Noyes wrote:
>
> David Douthitt, 2001-03-30 09:23 -0600
> >Let me see if I understand this right:
> >
> >* What I have now is "working directories" which include multiple
> >versions as well as compiled binaries.
> >* CVS would be source files only (with diffs and docs included)
> >
> >Is that right?
> Exactly! I couldn't have said it better. :)
Ahhhh.... things are becoming clear to me!
> >Then presumably the best thing to do would to get the
> >*.tar.gz file, the diffs, and then extract the tar.gz file, apply
> >necessary diffs, and let that sit (without the *.tar.gz) for CVS.
>
> You lost me.
1. Get source code tar.gz file
2. Extract source code:
# tar xzvf *.gz
3. Apply patches
# cd <newdir>
# for i in ../*diff ../*patch ; do patch -p1 < $i ; done
<adjust as necessary>
4. Leaving the source code tar.gz file is probably a better idea, so
there really isn't a step 4.
...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.
> >Two things:
> >
> >* I never created *.diff files for makefile only changes - such as
> >static libraries, and gcc options like -O2 -s -g
> >* I almost never added -s, leaving that to a "strip" done later.
>
> Now I'm completely lost. David, remember I'm not a programmer.
Okay.
> I'm a barely
> functional admin for this project.
I disagree vehemently! This project has better documentation than
I've seen almost anywhere else on Sourceforge; the PHPWebSite is
phenomonal.
> >* 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.
> >* 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.
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.
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
