Brian Cameron <[EMAIL PROTECTED]> wrote:
> > Please note that as long as there is no pkgadd(1M) on OpenSolaris, it does
> > not make sense to mention packages at all.
>
> Fair enough, regardless of how OpenSolaris is distributed, I suspect that
> there will continue to be a need to identify which interfaces are Stable
> for end-users. The place where interface stability is identified is in
> the Attributes section of the manpage. My suspicion is that the manpage
> will continue to be where users will look to find out this information
> (not the package prefix).
With a few exceptions (some nun Sun opensource packages), OpenSolaris does not
come with man pages.
> > If you like to discuss compatibility, you need to discuss whether it is
> > worse to have incompatibilities between current Sun Solaris distributions
> > and old one or whether is is worse when Sun Solaris differs from other
> > OpenSolaris based distributions that are derived from the same OpenSolaris
> > release.
>
> Another option is that OpenSolaris may exclude certain modules, and
> distributions who want to use OpenSolaris may include whatever makes the
> most sense for them. Once a migration path from ksh88 to ksh93 is in
> place, then upgrading OpenSolaris to include ksh93 as a default may make
> sense.
>
> The suggestion that both Solaris and OpenSolaris include /usr/bin/ksh93
> with Solaris including a /usr/bin/ksh symlink to /usr/bin/ksh88 and
> OpenSolaris including a symlink to /usr/bin/ksh93 might also be a
> reasonable way to work around issues like this.
This could be done starting with SchilliX-0.2 (next week).
> Providing both ksh88 and ksh93 might be the right answer for supporting
> both compatibility and stability.
Looks like a good idea.
> > OpenSolaris does not have packages.
> >
> > If you like to write text that applies to the OpenSolaris process,
> > give us pkgadd or don't write about packages.
>
> Sorry, I am not aware of what the process will be, or if it will
> include Solaris packaging.
Once the SVr4 package system is available, we could use it.
For now, the only way it to create tar archives and use them
as packages. This is what I did use for SchilliX.
To allow to to similar things as pkgadd does, I added some options
to star. A typical control file for SPS looks this way:
usr/sps/bin/gmake ? root bin
usr/sps/bin/make ? root bin
usr/sps/share/man/man1/gmake.1 ? root bin
usr/sps/info/make.info ? root bin
usr/sps/info/make.info-1 ? root bin
usr/sps/info/make.info-2 ? root bin
usr/sps/info/make.info-3 ? root bin
usr/sps/info/make.info-4 ? root bin
usr/sps/info/make.info-5 ? root bin
usr/sps/info/make.info-6 ? root bin
usr/sps/info/make.info-7 ? root bin
usr/sps/info/make.info-8 ? root bin
usr/sps/info/make.info-9 ? root bin
usr/sps/info/make.info-10 ? root bin
usr/sps/info/make.info-11 ? root bin
usr/bin/gmake ? root bin
As you see, there is a way to compile ad non-root and to create a tar
archive with the right permissions and owners.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-discuss mailing list
[email protected]
