On Saturday 16 December 2006 05:27, Geoffroy VALLEE wrote: > On Friday 15 December 2006 18:12, Erich Focht wrote: > Actually for OSCAR core and base packages it is almost done without any major > issue. Only one detail bother me a little bit: some OSCAR components, > available via pkgsrc, do not include a Makefile, basically we assume the > installation has to be done via RPMs. For the creation of Debian packages, it > is pretty nice to have a Makefile and it is also then simpler to maintain > both RPM and Debs. But as i said it is only a detail, it does not create any > strong limitations for the creation of Debian packages.
Oh, I understand. These are the pakages which have a serious %install section in the .spec file. IIUC you want to be able to do "make install"? There is typically no need to compile. Could be easilly done, I think. Let's aim for it for the 5.1 timeframe. > I do not see any benefit to automatically unpack and check-in packages. As > you > said we have two different kinds of packages: > 1/ packages that we develop and in that case it should be into pkgsrc; then > the creation of binary packages (RPMs and Debs) is not a problem (i already > started to integrate scripts for all these packages); moreover developers can > work together to be sure that everything is in pkgsrc, > 2/ packages that are developed outside of the project (such as SystemImager) > and in that case I have to contact the project to integrate mechanisms for > the creation of Debian packages. It is exactly what i did for SystemImager, > it works well (all projects are happy to see new contributors); i have for > example new SystemImager packages for Debian based on the "official > SystemImager release. There is a corner case: a type (2) package which needs a quick fix. Typically this fix is done as a patch and the patch is included in the .src.rpm . If you already have a debian make system in the package's source tree, we could use the "rpmbuild -bp" method to unpack and patch, after this you run the debian make stuff. It's a corner case between (1) and (2)... > So at the end, everybody seems to agree on the way to proceed. Is it in the > developer documentation? if no, should we add it (i am ready to do it)? I'd be thankful if you could add it! Best regards, Erich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
