> This is ambiguous.
You might very well be correct. I'll use a real world example to illustrate the
point I'm tried to make, below.
> I can only think of one instance where this
> behavior makes sense, but haven't dealt with IRIX to know if that's
> what you mean. Basically, the only time an OS update should *ever*
> muck with third party software is if the package in question was built
> by someone who's using it for an out of date rev of the OS, knowing
> that a later rev of the OS will provide a compatible replacement.
> Other than that, upgrading the OS should leave the third party
> software alone. That includes the case where I skip over any revisions
> the package author designated as suitable for replacing his package.
Example
sgi delivered (if my memory serves me correctly) openssh.
When I comiled my own OpenSSH, which was newer, I also packaged it as
openssh.sw, and inst(1M) picked it up as an upgrade, since the internal rev was
higher than that of sgi's own openssh.sw.
When it was time to go from IRIX64 6.5.15 to 6.5.16, sgi's version of
ssh.eoe.ssh naturally had a higher revision, and so, inst(1M) correctly marked
the openssh.sw.* subsystems for upgrade.
Perfect. I don't believe things could have possibly worked out any better than
that.
My supposition was, among other things, that NOBODY, and I do mean NOBODY knows
IRIX better than sgi (same logic applies to Sun and Solaris, IBM and AIX, and
hp and HP-UX). Going in position with this kind of thinking, sgi delivered
ssh.eoe.* subsystems that were perfectly crafted for their operating system.
And they did. Things just worked, beautifully. Sun really does the same thing,
at least we should credit the engineers there for attempting to do so. They
don't always manage to do it correctly because the open source software is
inherently unstable and mostly not well through through like traditional
products are, but they are getting better and better at it.
P.S. you actually made me power my Octane on, after such a long time. Picture
speaks a thousand words; /tmp/install is NFS mounted from a Solaris 10 (!)
system, serving out IRIX media:
# inst
Default distribution to install from: /tmp/install/IRIX/6.5.30-3of3/
For help on inst commands, type "help overview".
Inst 4.1 Main Menu
1. from [source ...] Specify location of software to be installed
2. open [source ...] Specify additional software locations
3. close [source ...] Close a software distribution location
4. list [keywords] [names] Display information about software subsystems
5. go Perform software installation and removal now
6. install [keywords] [names] Select subsystems to be installed
7. remove [keywords] [names] Select subsystems to be removed
8. keep [keywords] [names] Do not install or remove these subsystems
9. step [keywords] [names] Interactive mode for install/remove/keep
10. conflicts [choice ...] List or resolve installation conflicts
11. help [topic] Get help in general or on a specific word
12. view ... Go to the View Commands Menu
13. admin ... Go to the Administrative Commands Menu
14. quit Terminate software installation
Inst> open /tmp/install/IRIX/6.5.30-3of3/
Reading product descriptions .. 13%
Reading /var/inst/hist
Reading product descriptions .. 25%
Setting distribution to /tmp/install/IRIX/6.5.30-3of3/
Reading product descriptions .. 100% Done.
Inst> keep *
Inst> install openssh
Inst> conflicts
openssh.sw.server cannot be installed because of missing prerequisites:
1a. Do not install openssh.sw.server (1289636020)
1b. Also install openssl.sw.lib32 (1289635320).
openssh.sw.common cannot be installed because of missing prerequisites:
2a. Do not install openssh.sw.common (1289636020)
2b. Also install openssl.sw.lib32 (1289635320).
openssh.sw.client cannot be installed because of missing prerequisites:
3a. Do not install openssh.sw.client (1289636020)
3b. Also install openssl.sw.lib32 (1289635320).
Resolve conflicts by typing "conflicts choice choice ..."
or try "help conflicts"
Inst> conflicts 1b 2b 3b
openssl.sw.lib32 cannot be installed because of missing prerequisites:
1a. Do not install openssl.sw.lib32 (1289635320)
1b. Also install kerberos.sw.lib32 (1289615420).
Resolve conflicts by typing "conflicts choice choice ..."
or try "help conflicts"
Inst> conflicts 1b
No conflicts
Inst> go
Pre-installation check .. 8%
Checking space requirements .. 16%
Pre-installation check completed
Installing/removing files .. 16%
Installing new versions of selected kerberos.sw subsystems
Installing/removing files .. 36%
Installing new versions of selected openssh.man subsystems
Installing/removing files .. 59%
Installing new versions of selected openssh.sw subsystems
Installing/removing files .. 83%
Installing new versions of selected openssl.sw subsystems
Installing/removing files .. 94%
Removing orphaned directories
Running exit-commands .. 99%
Checking dependencies .. 100% Done.
Installations and removals were successful.
You may continue with installations or quit now.
Inst> quit
Requickstarting ELF files (see rqsall(1)) .. 100%
# showprods -l openssh
I = Installed, R = Removed
Name Date Description
I openssh 07/03/2008 OpenSSH server and client tools for 6.5.29
and later, 3.9p1-sgipl1
I openssh.man 07/03/2008 OpenSSH Online Documentation, 3.9p1-sgipl1
I openssh.man.manpages 07/03/2008 OpenSSH man pages, 3.9p1-sgipl1
I openssh.man.relnotes 07/03/2008 OpenSSH Release Notes, 3.9p1-sgipl1
I openssh.sw 07/03/2008 OpenSSH execution only env, 3.9p1-sgipl1
I openssh.sw.client 07/03/2008 OpenSSH Client Software, 3.9p1-sgipl1
I openssh.sw.common 07/03/2008 OpenSSH Common Client/Server Software,
3.9p1-sgipl1
I openssh.sw.server 07/03/2008 OpenSSH Server Software, 3.9p1-sgipl1
#
This is what the future of Solaris could be like.
Am I still being ambiguos?
_________________________________________________________________
Connect to the next generation of MSN Messenger
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
_______________________________________________
opensolaris-discuss mailing list
[email protected]
