Hi Daniel and Dimitri. Am 15.05.2007 um 19:54 schrieb Daniel Sperka:
> I have an interest in these packages, and if that group hasn't > started I'd like to volunteer to be the debian "maintainer" for > opensg. Yes, we're using OpenSG .deb-packages here, but the plan to make them public was cut by deadlines so far. We could also "donate" an edgy / feisty box for nightly builds - I'll have to check this (and have to find somebody / pay somebody for setting up a buildbot). > > At present I'm developing under Ubuntu, on AMD64, cross-compiling > for i386 distribution. I have ad-hoc installations of OpenSG libs, > but I will soon have a need for standardized openSG environments. Yes, apt-get install libopensg makes life _a lot_ easier if you have to maintain 5 - 15 machines. ;) However, our own packages have some additions that are not good enough (read: quck'n'dirty) to be "in the wild". > > I'd like to start with OpenSG 1.6, as that's the version I'm using. > Once that can be done, OpenSG 1.8 should be relatively easy. > Moving to scons at 2.0 will be more difficult, but I suppose I can > cross that bridge when I come to it. We're working with (nearly) current 1.8 cvs versions without problems, haven't tried 2.0 so far... > Ideally, I'd like to hear back from Dominik as to whether they've > managed to get a system up and running. If not, and if they'd like > some help, I'm ready. To be honest, I don't have that much to do with it, but I'm sure Dimitri will have some hints. I set him on bcc. > Dominik had proposed a fine-grained approach the the debs, i.e. > > libopensg-base > libopensg-system > libopensg-GLUT > libopensg-QT (maybe...) > libopensg-dev (headers, osg-config, ...?) > libopensg-source This is nearly what we did, but should be easy to change. Still open for discussion.. I tend to say you're right, it's a littlebit too fine grained (who uses system alone anyway? And if so, who cares about unnecessary 312kb optimized libopensgGLUT?) In fact, using apt it doesn't really matter, as it fetches all it needs by itselff if you install libopensg-GLUT > > My preference would be to consolidate this somewhat, to say.... > > libopensg (all libs except for, maybe, libopensg-QT) > libopensg-QT (maybe licensing requires us to separate this. > Will also require that any apps like fcdEdit be split into here). > libopensg-dev (includes headers, requires libopensg) Should be sufficient. As long as qt is optional. But even that should be no problem, as it doesn't taint your licensing as long as you don't link it.... But an additional libopensg-src with the debian build packages would be a good thing... Yours, Dominik ------------------------------------------------------------------------- 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/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
