I woke up the other day to discover this thing called "collision-protect"
available in FEATURES (ok, so I don't read my make.conf.examples too often). In
principal a good idea (make sure apache doesn't overwrite sun1 configs, etc.).
But now I (perl) has a problem, and I'm open to feedback (especially since its
advent a whole ton of bugs popped in bugzie about it). We are running into two
basic scenarios right now in perl - recommendations on what to tell people?
("drop your features" is doable, but I wanted to be nice about it)Type 1: Perl modules in dev-perl that replace those provided by the core perl install. Some are newer versions, some are security fixes, etc.. In the case of newer versions, you don't need them (so there's no justification for bloating and ripping apart the perl build) unless you happen to want to use something that does need them (say a gtk ebuild that requires a newer version of test than came with your core install - just an example folks) Type 2: Some authors include stubs of their other modules in everything they distribute. Carp-clan for instance can be found in all of that authors modules - there's the full intall version, but he also includes part of it (including the pods) in all of his other modules. Instance conflict if collision protection is on. Thing is, there's no reason to force people to install the full carp-clan (example for this case) if all they need is bit-vector. Thoughts? Yes, i've been informed in chat that perl is evil, our perl is evil, and that i might be the spawn of some belial kin, so that's already covered. -mike
pgpsh2NVPdLOY.pgp
Description: PGP signature
