Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 96954 - Patch Overlay similar to portage tree overlay
Summary: Patch Overlay similar to portage tree overlay
Status: VERIFIED LATER
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Eclasses (show other bugs)
Hardware: All All
: High enhancement
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-24 09:35 UTC by Matthias Hoermann
Modified: 2007-01-12 06:14 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Hoermann 2005-06-24 09:35:21 UTC
It would be nice for small scale changes in packages (e.g. I changed the 
frontend of btlaunchmany.py in bittorrent slightly) to have a directory where 
one can put patches that get automatically applied to the unpacked sources when 
emerging something. This should happen regardless of version (or at least in a 
range of versions) because otherwise there would be no real advantage over the 
current method to edit every installed minor version or revision ebuild. Ideally 
would be a file where such patchdirs can be specified for package versions 
similar to the package.use and package.keyword file syntax.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Radek Podgorny 2005-06-24 15:32:48 UTC
I'm second that. Having to dig into ebuild (and doing all the overlay stuff) is
a bit of overkill for simple things...
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2005-06-25 19:10:51 UTC
The complexity of Portage isn't low now and if you're able to apply a patch and
deal with the "consequences", you should be able to maintain your own ebuild in
your overlay. People are do not even rename the eclasses they copy to their
overlay and push their local problems to bugs.g.o because they forget about it
or are not able to track it down. With arbitrary patches this may become even
worse. I oppose such a feature.
Comment 3 Matthias Hoermann 2005-06-29 05:21:30 UTC
Most really useful features make it easier to break things but that doesn't mean
they should be thrown away without further thought. Perhaps applied patches 
could be listed in emerge info (or a similar command where the output can then 
be posted to the forum when someone has a problem), as should ebuilds in the 
portage overlay with some kind of checksum. Of course it should filter out the 
ones simply sitting in the overlay so only installed ones are listed.

Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2005-07-28 07:25:11 UTC
Putting a hold on feature requests for portage as they are drowning out the 
bugs. Most of these features should be available in the next major version of 
portage. But for the time being, they are just drowning out the major bugs and 
delaying the next version's progress. 
 
Any bugs that contain patches and any bugs for etc-update or dispatch-conf can 
be reopened. Sorry, I'm just not good enough with bugzilla. ;) 
Comment 5 Marius Mauch (RETIRED) gentoo-dev 2007-01-12 06:14:28 UTC
Doable with src_unpack hooks in bashrc now.