Hi Stuart, I second Erich and Michael: opkgc is still under development it is better to use the old format. However, i have a question for the group: is the documentation about OPKGs fixed? Last time i had a look at this documentation it was kind of out-of-date (some script names were wrong and so on).
Regarding OPKGC, if you want to have more details, i think you can have a very good idea of what you can do reading the documentation (but it seems you already did that) and the associated help (opkgc --help and opkg-convert --help). It is a pretty simple tool to use. But also remember that opkgc compiles an existing OPKG into binary packages, therefore if you develop OPKGs, you still need first to effectively create the OPKG. Let me know if you have any questions, i know few details about OPKGC and Jean (who implemented OPKGC) is currently on vacation. Regards, Le mercredi 4 juillet 2007 05:21, Erich Focht a écrit : > Hi Stuart, > > I agree with Michael, the best thing to do is to create a package in the > "old" format. That means you will need to write a config.xml, build RPMs > and put them into the distro/$DISTRO$VERSION-$ARCH subdirectory. Also put > the srpms to SRPMS/ . > > The basic idea of the new opkg format is to still keep the old format (with > some changes: new config.xml format, new API script names) including all > RPMs. This is something called "the developer view" of the package. A > package in developer view consists of: > config.xml > scripts/ > distro/.../RPMS and DEBs > SRPMS/ > [testing/] > [docs/] > > The metapackages produced by opkgc are not here, yet! Maybe we should/could > store them also in the developer view, but we didn't talk about that, yet, > AFAIK. > > For getting "the user view" we need to run opkgc to produce the > metapackages and move the metapackages as well as the RPMs to repositories. > Therefore the user will only need to see repositories. An opkg in that > format consists of - RPMs for the package > - RPMs for the metapackages, describing dependencies for client/master, > also containing the scripts/, testing/ and docs/. > > I hope that helps... > > Regards, > Erich > > On Wednesday 04 July 2007 04:17, Michael Edwards wrote: > > Well, one option is to make it in the current, better documented > > package format and convert it to the new format with a script which > > was written to convert the existing packages (also undocumented). > > > > As the documentation guy, I apologize, but I have not gotten around to > > looking at the documentation yet, let alone trying to make a package > > of some sort myself. > > > > If you have specific questions, I am sure Jean or someone else > > familiar with opkg will try and answer them. > > > > On 7/3/07, Stuart Archibald <[EMAIL PROTECTED]> wrote: > > > Dear all, > > > > > > I have just had a quick word with bernardl on IRC and he said to bring > > > to your attention that I feel that there are some documentation/clarity > > > issues to do with OPKGC. I am struggling and want people to know why so > > > things can be made better. > > > > > > I have been plodding along with MPITB (MPI Tool Box) for GNU Octave > > > packaging and development and have got to the stage where I want to > > > package up my rpms so that they become an OSCAR package. So I went to > > > the wiki and unfortunately got very confused... > > > > > > I first visited > > > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/BuildOpkg > > > this page give a brief, "you need to build packages this way now" > > > message and points you to > > > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/opkg_opkgc > > > . This page points you to a svn co of opkgsrc/tools/opkgc which I > > > couldn't find, I guessed after a while that it meant here: > > > http://svn.oscar.openclustergroup.org/trac/oscar/browser/pkgsrc/opkgc > > > > > > I am not sure if the wiki pages are just unfinished but their > > > fragmentation made them hard to follow. > > > > > > On building and reading the docs from svn I am greatly confused about > > > how to use opkgc and what I need to do to get my rpms into a package. > > > The old manual has some comprehensive instructions on how to actually > > > make a package and I feel confident that I could do so. Whereas I feel > > > that the docs on opkgc/opkg are good at describing why and what the > > > tools do but not how to use them for development of packages. I realise > > > that this is devel stuff and docs tend to come later and I appreciate > > > the effort to make things easier via opkgc. > > > > > > Sadly, I'm not sure how to even start, I will figure it out eventually > > > as I usually do, but not coming from a computing background clear "this > > > is how you do it" instructions would be lovely. I'll try and remember > > > to make notes as I *slowly* plod along providing I can figure out how > > > to go forwards and perhaps they could be used to start a manual. > > > > > > Thank you for your time, > > > > > > Kind Regards, > > > > > > Stuart Archibald (Imperial College London.) > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Oscar-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-devel -- Geoffroy ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
