[companion-discuss] Stupid User (or Usability) question

[Dennis Clarke]

>
> On Jan 4, 2007, at 1:09 PM, Keith Bierman wrote:
>
>> Having had some issues with the CUPS installation from blastwave
>> with a particular nevada build+local environment I figured I'd try
>> the companion CD version just to see if that cured things (of
>> course, blastwave's worked fine with a previous nevada build (51)
>> so I'm betting it's something changed in nevada_current ;>). But
>> that's not the point of my post, just background.
>>
>> wget (wgot?) the entire CD and then looked for CUPS. Not a problem,
>> but pkgadd -d SFWcups etc. resulted in some warnings about needing
>> other packages. So pkgadded them, etc. This seemed a whole lot more
>> tedious than the blastwave pkg-get ....
>>
>> Am I missing something about pkgadd usage, or have we built the
>> companion packages in a way that's suboptimal (viz.  adding a bit
>> of functionality should appear more like adding functionality ...
>> not playing hunt the needle ;>)??
>
> Oh, and I neglected to mention that despite it being loaded, it's not
> actually running (even with a reboot) ... as opposed to the pkg-get
> which ended up with CUPS running even sans reboot. No doubt, there's
> some critical step or document I failed to read ... clues appreciated!

perhaps a red herring here but do you think that this may be related to a
printing issue with SNV_51 as opposed to the CUPS software?  I think that
Rich Terr reported some problems that have been fixed in snv_54.  Perhaps
you could try snv_54 and then you would be at the current Nevada release.

I know that is a bit of a big job, sorry.  I just don't see how software can
go from working on Solaris 8 and 9 and 10 and Nevada up to build 50 and then
suddenly stop while others have seen problems with printing in snv_51 ( or
thereabouts ).  It all seems connected you know ?

So your best best is to try installing snv_54 and then pkg-get -i cups

wdyt ?

-- 
Dennis Clarke