John Darrington <[email protected]> skribis: > On Fri, Feb 14, 2014 at 11:59:32AM +0100, Ludovic Court??s wrote: > However, we???re just packaging an existing application. IMO, when we > find such limitations (it???s really a limitation, and not something that > makes it completely unusable), we should submit the improvement > upstream, unless upstream no longer exists (I???m not sure if this is the > case here.) > > > I think the following are true (please correct me if not): > > * Most (all?) the files in gnu/packages/patches fall into the category of > "limitations" to upstream. > > * In principle, those patch files could be directly applied to upstream > without modification.
I think most of the patches in there are fixes (normally submitted upstream), or adjustments so that things can build/run in our environment (patches we don’t want to submit.) > This being the case, would it not be a good idea, to have some kind of web > interface to these patch files to make it easy for upstream maintainers to > fetch them. (perhaps there is sucha page already) Yes, the page is: http://www.gnu.org/software/guix/package-list.html It lists patches and ‘patch snippets’ for each package. Ludo’.
