Yes, your mechanism is doable - no it's not good enough :) Take it from me as the creator of possibly the most complete slackware derivative distro out there. I build several hundred packages every single month - there are a LOT of rules you need to comply with to do it RIGHT. See "The perfect package" on linuxpackages.net - and that is just the start.
Also see mkpkg - my toolkit to automate most of the steps. This is why Patrick uses slackbuild scripts. The script I created for lazarus is very nearly a slackbuild script, but written to fit into the rest of the packaging scripts provided. It uses most of what mkpkg does - but predone. Basically, I wanted to make sure that if somebody submitted a package created with my script to Pat - that he could not turn it down on grounds of ANYTHING structural. Furthermore my packages also use the common slackware extensions for example creating a slapt-get dependency listing. Ciao A.J. On Thursday 14 September 2006 22:23, Andrew Haines wrote: > Andrew Haines wrote: > > here's what I did: > > ........ > > > cd ../ (/tmp/slackware) > > > > tar -cf lazarus-version-arch.tar > > should be > tar -cf lazarus-version-arch.tar ./usr ./install > > Andrew > > _________________________________________________________________ > To unsubscribe: mail [EMAIL PROTECTED] with > "unsubscribe" as the Subject > archives at http://www.lazarus.freepascal.org/mailarchives -- "80% Of a hardware engineer's job is application of the uncertainty principle. 80% of a software engineer's job is pretending this isn't so." A.J. Venter Chief Software Architect OpenLab International | +27 83 455 99 78 (South Africa) http://www.getopenlab.com | 086 654 2898 (Fax) http://www.silentcoder.co.za | +55 118 162 2079 (Brazil) GPG Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x27CFFE5A
pgpDU8W7HkkDg.pgp
Description: PGP signature
