Am Dienstag, 22. M�rz 2005 18:04 schrieb Charles Steinkuehler: > K.-P. Kirchd�rfer wrote: > | Am Dienstag, 22. M�rz 2005 17:33 schrieb Charles Steinkuehler: > > <snip> > > |> What's the easiest way to 'tinker' with creating a new package? > |> It looks like I need to put the initial package files online via > |> http or viewcvs, and add an appropriate <server> section to > |> conf/sources.cfg. > |> > |> Is this correct, or is there support for 'local', or file:// > |> type of access, so I could just make a local "repository" with > |> the source tarball and buildtool config files, and not hassle > |> with network downloads? > | > | A quick'n'dirty solution is to create a directory for your app in > | buildtool/sources > | like > | buildtool/sources/rsync > | > | Copy your source tgz into that dir and create there buildtool.mk > | and buildtool.cfg (you may copy existing ones and change as > | needed). > | > | You'll have to add the new package to conf/sources.cfg like any > | other - don't bother about server/network stuff - with all > | needed files in sources/yourpackage it will not try to download > | again. > > Thanks...I didn't realize it wouldn't try downloading if the files > are already there. > > So far, the only thing that seems odd about buildtool is the > centralized file with all the servers, sources, and packages > (conf/sources.cfg). The files for building each package are > already seperated per-package, so it seems like this should be > multiple files and/or directories as well, ie: > > ~ conf/servers <- File with server entries > ~ conf/pagkages/ <- Directory > ~ conf/packages/mypkg <- Single entry > ~ conf/sources/ <- Directory > ~ conf/sources/mysrc <- Single entry > > ...but I have no idea how easy/hard this would be in perl (yes, > I've fallen to the point of suggesting new features/functions w/o > offering any coding assistance! :). It just seems that having to > modify the entire sources.cfg file to add/remove a package is going > to get cumbersome eventually...
Good point - sources.cfg becomes somewhat too big - it's been good to start with buildtool - but I can see improvements... > | If you like, I can send you the rsync setup and the corresponding > | entry for sources.cfg as example. > > Please do. Will do off-list. > Also, what's the preferred method to provide files for a new > package so they can be included in CVS? A tgz file of sources/pkg > and a diff of conf/sources.cfg, or some other method? Every LEAF developer has write access to our cvs "contrib" repositories (buildtool setup and sources as well as lrp's). A diff for sources.cfg send by mail - either private or on leaf-devel, should be enough. Lrp's committed to contrib section will be added to the packages page on LEAF Bering-uClibc pages as well. We can also offer you access to our complete cvs tree (includes write access to buildtool :)). kp ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_idh82&alloc_id148&op=click _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
