George Vasick wrote: > I took the versions directly from the GCC shared libraries: > > libgcc_s.so.1 > libgfortran.so.3.0.0 > libgomp.so.1.0.0 > libobjc.so.2.0.0 > libobjc_gc.so.2.0.0 > libssp.so.0.0.0 > libstdc++.so.6.0.10 > > I was planning to track the actual GCC versions for these packages. > > Alternatively, I could combine all of these libraries into a single > package, something like developer/gcc/gcc-runtime-4 with a version > number of 4.3.3. This may be simpler for users you just need the > libraries to run already compiler applications.
It's probably best to keep them in separate packages, for minimization purposes. Most folks aren't going to need libgfortran of libobjc on their systems, for example. And if any of the libraries are big, then there's extra incentive to have them divided. As for versioning, you can track either the version of the tarball they come in or you can track something deeper about the library, like what you're doing currently. Note that for some opensource libraries, the versions will stay at the same number for a long time, even though it's undergone major (if not necessarily Major) change over that period. If the library versions aren't evolving, then you might not want to use them as the package versions, which for many cases people will expect to match the tarballs. You can evaluate this specific situation better than I can, I'm sure. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
