I am in favor of dropping Solaris 9 and maybe making sure our last Solaris
9 packages are somehow stable, as James advised.
Option 2 might be possible but it would need to be a light subset so we can
support it without too much work.
But it brings some new questions:
- how large would be the subset of package ?
Where do we stop exactly: GAR + compiler, + interpreter, + basic
libraries... ?
- would this subset really satisfy the request we receive about Solaris 9
?
Compiling a package often requires a lot of dependencies. The users
might not be so happy when they see the numbers of softwares they will have
to compile by themselves to be able to compile the software they're
interested in.
- how often do we have this kind of Solaris 9 request ?
It would be interesting to know how many times we are contacter about
this, to know if it is worth it.
Personnally I don't use Solaris 9 anymore and I prefer to focus on Solaris
10 / 11 packages during my opencsw time.
Yann
2013/8/7 İhsan Doğan <[email protected]>
> Am 05.08.2013 15:37, schrieb Maciej (Matchek) Bliziński:
>
> > 1. Don't do anything. When it breaks, it remains broken. We'll make an
> > announcement when this happens.
> > 2. Support a subset of packages for Solaris 9, such as cswclassutils,
> > and GAR with friends. If it turns out to be too much effort, we stop
> > supporting Solaris 9.
>
> Option 1.
>
> Actually, I would already start to break Solaris 9 support. Solaris 9 is
> EOL and Solaris 10 is already out for 10 years.
>
>
>
>
> Ihsan
>
> --
> [email protected] http://blog.dogan.ch/
> _______________________________________________
> maintainers mailing list
> [email protected]
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.
>
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.
