[csw-maintainers] libproxy in testing

[Roger Håkansson]

Dagobert Michelsen wrote:
> Hi Roger,
> 
> Am 14.01.2010 um 13:55 schrieb Roger Håkansson:
>> Dagobert Michelsen wrote:
>>> Hi Ben,
>>> Am 05.01.2010 um 22:01 schrieb Ben Walton:
>>>> Excerpts from Dagobert Michelsen's message of Tue Jan 05 15:56:02 
>>>> -0500 2010:
>>>>
>>>>> be needed. Thoughts?
>>>> 10 only.  If the devs aren't interested in older platforms and you
>>>> have no personal need, why go through the headache?
>>> The question is: Do we want to release it and make separate releases
>>> of packages for Solaris 8/9 vs. 10 which require it?
>>
>> libproxy is a requirement for some gnome-packages which would mean 
>> that we can't upgrade upgrade them without libproxy, and since some of 
>> those packages have dependencies on other packages which might get 
>> upgraded we would soon end up with a lot of Solaris8-packages which 
>> doesn't work.
> 
> The alternatives would be:
> (1) wait until the project switches to C++ (should be done pretty soon)
>   where the standard is supported by SOS11.
> (2) Use GCC to compile libproxy. This would pull in gcc*rt, but would
>   work fine.
> (3) Start with Solaris 10. By definition we start at Solaris 9, although
>   the download stats say almost all people use Solaris 10 by now
>   (see http://wiki.opencsw.org/suggestions  mirror stats if you are
>   curious).

And (4) Use my patches to build Solaris8-packages.
There are only minor changes needed to get it working. The ones I've got 
are not that generic that they could be submitted upstream, but for our 
purposes they work.
However, I can't get the Makefile working so packaging on both Solaris 8 
and 10 works with the same Makefile (maybee not needed if only 
Solaris8-packages are to be released).
But I can commit my changes so you can finish the work.