Alan: >>> The following list seem like things needed to build firefox, but which >>> don't need to be shipped to users of firefox - is there some reason >>> these are needed, or is it just an artifact of the spec-files build >>> system? (Though it would seem easy enough to just not deliver the >>> -devel packages for private components to the WOS.) >> >> Some other teams have requested availability of some of the newer >> libraries through contracts. These files will allow those teams to link >> to the newer versions easily. If there is some other formal way in which >> these can be made available to those teams, there is no need to ship the >> -devel packages. > > You can deliver the -devel packages to those teams without delivering them > to all customers, or you can deliver them to the WOS and accept that > customers may see them and try using them. (The -private in the directory > name should be a strong clue that they shouldn't expect support for them.)
Personally, I think there is value in delivering the devel packages and the pc files. They are clearly in a private directory, so anyone who uses them should know they are unsupported without a contract. Making it possible for people to build newer GTK+ based programs on S10 if they desire, even if in an unsupported fashion, will be a big benefit to some people, I think. Also, it is much easier for other project teams to use the interfaces with a contract if the -devel packages are not delivered separately. Brian
