I think these are two different problems. I agree with you, it should be nice to not check-in binary packages. But we also need a nice procedure for the creation of those binary packages, especially since we will have to deal with different formats.
Currently i just try to figure out what is the best solution to address the second issue. If we can all agree on one way to proceed, it may be interesting to add that into the developer documentation in case new developers join the project (they will have then the description of the procedure for the creation of new releases for OSCAR components). Does it make sense? or did i miss your point? Le vendredi 15 décembre 2006 12:54, Michael Edwards a écrit : > Would this be in preference for checking in the binary packages, or in > addition to it? > > I would think it would save space the repository if we only kept the > source checked in and just make the binaries as part of the nightly > build process or something like that. Or is this outside the scope of > what you are talking about. > > Just thinking out loud... > > On 12/15/06, Geoffroy Vallée <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I try to complete the basic port to Debian and Erich did the following > > comments during one of our email exchange: > > "Actually many RPMs are not in the pkgsrc, so nobody should simply expect > > to find it there... > > Geoffroy, can't you just build a deb with alien?" > > > > The answer is definitively no, i cannot use alien. Alien cannot create > > good packages: > > - dependences are not handled correctly, > > - the final package is not compliant with Debian policies. > > > > So my general question is the following: why do we not manage binary > > packages in a better way? Today, all the code for OSCAR packages is not > > available via pkgsrc (svn), and if the code is in svn, tags are not > > created for each new release. Based on that it is very difficult for me > > to match the version of Debian packages to the version of RPM packages. > > Therefore, it is very difficult to maintain OSCAR on Debian. > > I like the idea to have the code of the different OSCAR parts in the svn > > repository and create tags for new release. This is not really time > > consuming and at the end, it is pretty neat to maintain both RPMs and > > Debs. But all developers have to accept this rule. > > > > Any thoughts? > > > > Regards, > > -- > > Geoffroy > > > > ------------------------------------------------------------------------- > > 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 > > ------------------------------------------------------------------------- > 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 -- Geoffroy ------------------------------------------------------------------------- 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
