Jonathan Edwards wrote:
On Aug 25, 2009, at 9:12 AM, Darren J Moffat wrote:
4. You want package A but not package B that it depends on. (Or packages
C, D, E, F... that get pulled in.) Am I managing the system, or is
the system
managing me?
Why would you want that if A really does depend on B,... ?
Isn't this just another case of 3 ?
A couple of example cases for this:
(1) a package contains a binary or driver you might want, but you don't
care about the GUI component that's also in the package .. the GUI
dependencies are "require"d but you don't really want them since you
don't want to pull in the entire windowing environment.
Arguably that is a packaging bug and there should be 2 (or maybe more)
packages there.
However that doesn't help if you can't influence the upstream packager.
(2) there's no mechanism for an OR .. in other words - let's say that
package A has a requirement for a certain library, but that requirement
could be met by either package B (which pulls in packages C, D, E, F) ..
or package X (which only pulls in packages Y and Z)
I find this one a very interesting case.
There are a number of things which need a "database". Sometimes they
can be built to support one or more of sqlite, mysql, postgres. So this
is a good example of an optional dependency. I might not want to deploy
using mysql so I don't want it installed.
(3) the customer has their own custom packages which provides proper
dependencies for package A and knows this.
I don't think this one needs a force, I think it just needs the local
repository to have an entry for 'A' that specifies the alternate set of
dependencies. Then the local repo is preferred. I think this will
work, because I believe I managed to do something like this to get stuff
installed from /pending when there was a missing ncurses dependency.
(4) there is a known security issue with package E .. hence no easy way
to extract that package from the mix and replace it
I don't think security bugs shouldn't be special as far as the package
system is concerned.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
