On 12/ 2/11 08:26 AM, Rich Burridge wrote:
On 12/01/2011 09: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.
That said, Norm can tell you it's okay to start letting these things
slide,
and I won't tell a soul.
I see that Norm has filed a couple other related bugs, and from the
comments in CR #7117301, it looks like he'd like me to fix that with
at the same time that I fix this one.
So new webrev at:
http://jurassic.us.oracle.com/~richb/7116962-v2/
The final published manifest for the .../apache2-modules/mod_perl
component is at:
/net/stard.us.oracle.com/tank/ws/UL/7116962/components/apache2-modules/mod_perl/build/manifest-i386-apache-perl.published
I reran the double install test and it's working fine.
Norm, is this fix okay with you?
seems ok to me.
-Norm
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
