2010-08-04 14:01, Bertrand Juglas skrev: > When i've looked at the lxtask recipe i've seen it was created 2 years ago > but not updated yet and the only method redefined from AutoPackageRecipe is > to define the download location template. > Would it be possible to define a generic LxdeRecipe heriting from > AutoPackageRecipe but redefining the download location template ? > With this LxdeRecipe, all LXDE recipes should be easier and also more > maintenable. > Have I well understood how recipes herits from generic recipes ? > > Le 4 août 2010 à 07:26, Martin Bähr<mba...@email.archlab.tuwien.ac.at> a > écrit : > >> On Sun, Aug 01, 2010 at 10:42:02PM -0400, richard kim wrote: >>> For example, I looked at VLC recipe, taken from http://www.rpath.org/web/. >>> The "def setup(r):" requires r.macros, rConfigure, rMake, etc. I vaguely >>> understand what these commands do, but it gets worse. I do not understand >>> even the concepts of their use. >> are you familiar with compiling applications from source (without >> packaging them?) iaw: are you familiar with the general way to build >> source using configure; make; make install; etc. >> if not, i am happy to elaborate. >> >> if you have compiled source before, have you noticed that sometimes >> configure or make need extra arguments to make things work? >> >>> 1. When do you use these commands? Why do some packages need them, and >>> others do not? >> you need them when an application requires extra arguments or settings >> and the defaults are not good enough. >> >>> 2. How do you figure out some of the needed options? example: >>> r.Install('vlc.png', '%(datadir)s/pixmaps/vlc.png'). Where did the >>> 'vlc.png', '%(datadir)s/pixmaps/vlc.png' come from, and how can I figure >>> that out in the future for other packages? >> something like this is usually noticed when you install the application >> and find something missing. it happens that the developers of an >> application forget to copy files during the install process because they >> usually test the application without installing it. it can also happen >> that you want to add files to a package which are not part of the >> package. (common with desktop icons for example) >> >>> I have been thinking that looking through existing packages might be helpful >>> to learn, but I would like to start simple, learn, and go from there. So >>> far, doing this exercise, I find a command, look it up, and I still don't >>> get it. Maybe if someone knows of very easy packages with only 1-2 "r." >>> parameters (sorry, not sure of the official name of these), I can start from >>> there. >> do you have a specific packaging goal in mind or do you want to just >> learn packaging in general? if you are looking for random examples then >> maybe you want to check: >> http://wiki.foresightlinux.org/display/DEV/Packaging+Tips#PackagingTips-Howtocheckoutallrecipesintherepository >> to get all recipes and then browse through them. >> >>> Anyone else have any suggestions for a complete beginner, for learning >>> without getting overwhelmed? >> focus on a set of packages interesting for you. ignore to dificult >> packages. (don't try to solve hard problems until you feel confident) >> >> if you don't know what to pick, but want to do something worthwhile, you >> could take a look at LXDE. those packages are not to hard, and they need >> some updating. i am also hoping that we can move them into the main >> foresight repo some day (they are in lxde.rpath.org for now) >> >> see http://www.rpath.org/web/repos/lxde/browse?char=L for the recipes. >> >> greetings, martin. >> -- >> cooperative communication with sTeam - caudium, pike, roxen and unix >> searching contract jobs: programming, training and administration - anywhere >> -- >> pike programmer working in china community.gotpike.org >> foresight developer (open-steam|caudium).org foresightlinux.org >> unix sysadmin iaeste.at realss.com >> Martin Bähr http://www.iaeste.at/~mbaehr/ is.schon.org >> _______________________________________________ >> Foresight-devel mailing list >> Foresight-devel@lists.rpath.org >> http://lists.rpath.org/mailman/listinfo/foresight-devel > _______________________________________________ > Foresight-devel mailing list > Foresight-devel@lists.rpath.org > http://lists.rpath.org/mailman/listinfo/foresight-devel
We got a LXDE repo, needs a cleanup though. using wrong group in it. (or the iso was built from wrong group) http://www.rpath.org/web/project/lxde/ Maybe LXDE packages/recipes should be copied to foresight repo instead? Tomas Forsman -- Foresight Linux Developer http://www.foresightlinux.org Foresight Linux - SE http://www.foresightlinux.se Tomas Forsman - Blog http://www.foresightlinux.se/blog/ _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
