From: Brian P. <br...@pr...> - 2000-06-26 15:47:40
|
Hward Luby wrote: > We can do that for Red Hat. Since it's only one file, we'll make a > compressed .so. Do you want us to host it or should it go on sourceforge? There's the libGLU.so library and glu.h header file. Is it standard practice to put the library and header in the same package? It would be the simplest for most people. I'm not sure of the best place to host it right now. The SGI SI site might be best. Olivier Michel wrote: > Ok, so I am volunteer to do a re-packaging for SGI GLU. I plan to do the > following: > > 1) remove everything else than GLU (i.e., GL, GLX) from the SGI SI > package. Hopefully the main/gfx/lib/glu/ subdirectory can stand on its own. That is, it doesn't have intimate dependencies on the rest of the sample GL source tree. > 2) get rid of C++ dependencies since I believe they are useless for GLU. I think the GLU NURBS tessellator is written in C++. > 3) create some standard and easy way to build (like the GNU > ./configure;make;make install but also the old style "make target" as > used in Mesa) > 4) create one RPM source package and two binary RPM packages (Linux i386 > and Linux PPC) There are already GNU makefiles within the tree. It would be nice if you could add rules to generate the binary and source RPMs and have those rules put into the SI's CVS tree. I think binary RPMs are the most important thing initially. People can download and compile the sources now but probably >95% of people just want to simply install the library and header files with minimal fuss. > I am currently printing the license B from SGI to understand how I can > remove parts / add new things. I encourage you to work in cooperation with the SI developers/maintainers rather than branch off. I think they'd be receptive to someone helping with packaging. Perhaps you guys should join the SI mailing list and discuss your plans there. I'm sure a lot of people would appreciate you doing this! -Brian PS: A similar treatment for GLUT would be nice too. |