On Tue, Oct 15, 2013 at 1:04 PM, P.C. <[email protected]> wrote: > > Is that "ebuild decay" intentional? How long I can expect ebuilds to > stay useful?
There really are no guarantees for anything not in the current tree. The EAPIs/eclasses themselves are pretty well-designed and while breakage over a period of years is likely, over a period of months it is not. However, your problem is that a patch set was hosted only on mirrors and not anywhere more permanent. In general mirror-only patch hosting is frowned upon - they should have a SRC_URI that doesn't start with mirror://. However, that doesn't guarantee that those patches will be hosted forever. I keep them in my gentoo webspace and don't really rush to clean them up, but that space is not archived anywhere. Google suggests that you might be in luck if you manually fetch your file from here: http://dev.gentoo.org/~floppym/python/ I think there might have been a little talk about better solutions for file-hosting that might address some of these problems, but I'm not aware of any serious work being done. Rich
