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.
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) Then we can publish this
page and say "hey upstream maintainer! Your package has limitations.
Please apply these patches."
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
