On Sunday 30 March 2008, Mark Loeser wrote: > Mike Frysinger <[EMAIL PROTECTED]> said: > > On Sunday 30 March 2008, Mark Loeser wrote: > > > Actually, I'd say this should just be removed. If a user wants to > > > apply a patch, they can put their own ebuild into an overlay and do it > > > themselves (presumably if they want to patch something, they'll know > > > how to make the simple modifications to an ebuild). By allowing the > > > user to arbitrarily patch something means we have no idea what the user > > > has built and is filing a bug about. If they installed an ebuild from > > > an overlay it is a lot easier to identify what they built. Sure, they > > > could patch the ebuild in their tree, but by supporting user supplied > > > patches easily in this way, we are encouraging them to patch things > > > without our knowledge. If we start supporting this across the board, I > > > can see bugs being filed when their patches break and they don't > > > understand what is happening. > > > > that's actually exactly what i'm encouraging. i'm not worried about such > > issues as they're easily resolved by people posting the full build log. > > Which is great, but I think this is something we should discuss and > figure out if this is something we want to introduce into the tree (too > late now, but better late than never). If it is something we want to > move forward with, it should be introduced at the package manager level > instead of being an in-tree package manager specific feature. > > I'm coming at this from a QA perspective and if we want to do it for one > package, it should be introduced for all. We should document it and > know how to support it as well.
there is no package-manager specificness here. it's already completely doable from a user perspective, just having it in the ebuild makes my life and users' lives easier. i'm using it in packages that tend to have a lot of extraneous patchsets associated with them. the random patches were punted from ebuilds and now it's up to the user to maintain the feature sets. -mike
signature.asc
Description: This is a digitally signed message part.
