buildpkg.sh scripts problem

[Nicolas Williams]

Well, what I do here, generally, is:

 - make -e DESTDIR=... install
 - build prototype file, using relative paths, based on what got
   installed in $(DESTDIR)

I have a bunch of scripts to support doing this for prjects with
source, and for dealing with edit scripts and various things.

And yes, it's proprietary... But you can steal the approach :)

Nico


On Thu, Nov 08, 2001 at 02:58:42PM -0600, mouring at etoh.eviladmin.org wrote:
> 
> 
> On Thu, 8 Nov 2001, Nicolas Williams wrote:
> 
> > Make a static prototype file.
> >
> No..
> 
> We moved away from a static prototype due to the fact it was ignored and
> kept falling out of sync.   I really don't wish to return to it.  I'd
> rather see an automatic way of generating such a file.  Even if it costs
> me a few more lines.  Not as if 'buildpkg.sh' is that complex. =)  It is
> under 90 lines, and very readable.
> 
> - Ben
> 
--

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.