On Mon, Dec 21, 2009 at 9:27 PM, Gary Law <[email protected]> wrote: > All > > We seem to be stuck here with a choice, and to avoid lots of quoting > I'll summarise: > > 1) Use CSWcswclassutils and stop those with read-only /usr using our packages; > > 2) Migrate away from CSWcswclassutils and build another mechanism > that's similar. > > Primary problem with (1) is it rules out using CSW packages on a > significant number of machines which have read-only /usr. I'd call > that a major issue, a showstopper bug in the case of the package I'm > trying to get into GAR.
Sad to hear that. > Primary problem with (2) is that we might end up having users have to > answer 'yes' to postinstall script questions if they don't have the > right sort of admin file set up. Minor issue IMHO. > > I'd say the benefits of fixing (1) massively outweigh the disbenefits > of (2). Thoughts? I agree on the point that answering 'yes' to the postinstall scripts is a minor issue. If one maintains numerous of Solaris machines, automated package installs are a must. Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
