Randy McMurchy wrote: > Randy McMurchy wrote these words on 01/08/06 21:50 CST: > >>Bruce Dubbs wrote these words on 01/08/06 21:38 CST: >> >> >>>Editor creates aKode-version.tar.bz2 file for the mirrors. >> >>Yes, not too difficult once you figure out KDE's idiosyncracies. > > > And here is our choices: > > 1) Direct the user to download via SVN the required directory. > This sucks because the user may not have SVN installed on his > machine. Additionally, there are other software directories in > the downloaded directory that will get built and installed > unless you give alternate commands. > > This almost rules out this choice. Which leaves us with: > > 2) Host the tarball ourselves. > > Which means an Editor must download via SVN, and remove 5 > directories from the root of the tree. This leaves a created > tarball of: > > -rw-r--r-- 1 rml install 650636 Jan 8 20:22 akode-svn.tar.gz > > 650 KB. Then, you must run an obscure command of > > "make -f Makefile.cvs" to create the autotools using the special > KDE method. Once you run this command and tar up the files you > have: > > -rw-r--r-- 1 rml install 1421912 Jan 8 20:24 ready2go.tar.gz > > More than twice the size, but ready to run CMMI. > > Which tarball should we host?
I think we need to host the smaller tarball ourselves and tell the users where we got it. Then we tell them about the "make -f Makefile.cvs" so they can do it themselves if they get a different version directly from the KDE SVN. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
