On 12/ 1/11 11:37 PM, Danek Duvall wrote:
Rich Burridge wrote:
http://jurassic.us.oracle.com/~richb/7116962-v1/
Should've done my homework. Turns out SUNWapch22u included all of what got
split out into apache-perl. I don't think it's worth keeping a bunch of
legacy actions around in packages like this -- they really need to be
delivered in a different way entirely -- but as long as the policy is to
have legacy actions in each package that delivers bits that went into SVr4
packages, then I'm guessing the right answer here is to actually make the
action match the one it's conflicting with.
I think that removing the legacy action from the apache-perl action is
the right thing to do here. The apache-perl package includes mod_perl
support for the apache-22 server, so for it to be of any real value, you
have to install the apache-22 package on the system, which gives you the
legacy action. Actually, the fact that the apache-perl package doesn't
end up with a dependency on apache-22, seems like a bug to me (7117301
apache-perl should probably depend on apache-22).
That said, Norm can tell you it's okay to start letting these things slide,
and I won't tell a soul.
Danek
_______________________________________________
This (and an IRC discussion I had last week) has prompted me to file
7117296 legacy actions need some love
Since you are already in there, 7117301 should probably be addressed
when this is. 7117296 will require more work.
I think it's time for bed.
-Norm
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
