On Thu, 2005-07-21 at 03:33, Joerg Schilling wrote: > Darren J Moffat <[EMAIL PROTECTED]> wrote: > > > On Wed, 2005-07-20 at 14:04, Chris Ricker wrote: > > > creating a mysql-4.1 pkg from scratch. Or what if you want the same > > > version that Sun shipped, but just need it compiled with different > > > options? That's trivial on Linux distros, not so trivial on Solaris.... > > > > Thats what the SUNWmysqlS package is for, it is intended to > > be almost equivalent to the source rpm. However rpm is both a build > > and package system the SVR4 package system isn't. > > I don't see anything in rpm that could not be handled via the pre and > postinstall scripts that are part of a SVR4 package.
The way that rpm works is that it is used to drive make and cc and then assemble the .rpm file. It is designed to be able to run from a simple .spec file. I guess you could do this in pre/post install script for source packages, and interesting idea Joerg! > This only contains a rough description in prosa but no build system. > > For GPL'd software, it violates the GPL as the build scripts are > not available. I think you are talking about this text from GPLv2 "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable." The scripts used to control complication are the configure scripts and makefiles that come with the original tar balls. Those are included, in addition we include the flags we passed to configure. I don't see anywhere where it says that the vendor shipping the binary executable must provide you with every single possible flag they passed to ./configure and every environment variable they set when running configure or make. The GPL also doesn't imply that the person provided with the source needs to be able to generate an exact duplicate of the binary, which is what I believe you are trying to do based on the previous times you have brought this up (a good thing to try and do though). I also believe that what Solaris does with the source pacakges is equivalent to what other distributions do with source rpms, but I could be wrong but I'm far from being an expert on how to use rpm to drive builds. I personally think you re stretching the intent of this paragraph and I personally don't believe we are violating the GPL but then neither of us is a lawyer. Note also that what was done for the source packages in Solaris is approved by SunLegal so some level of legal analysis was done for this. Note also that for the GNOME bits we do use rpm spec files to build and do ship the full build environment. -- Darren J Moffat _______________________________________________ opensolaris-discuss mailing list [email protected]
