Re: How to contribute a patch to a macports patch

On 5/20/16 10:19 PM, David Antliff wrote: > On Sat, May 21, 2016 at 12:55 PM, David Evans > wrote: > [snip] >> If you want to submit a patch, the clearest way IMO is to submit your >> changes as a patch against the original, >> unmodified file. Then, if an existing pa

Re: How to contribute a patch to a macports patch

On Sat, May 21, 2016 at 12:55 PM, David Evans wrote: [snip] > If you want to submit a patch, the clearest way IMO is to submit your changes as a patch against the original, > unmodified file. Then, if an existing patch exists, mention that this patch should replace that one. Or you > can give yo

Re: How to contribute a patch to a macports patch

On 5/20/16 4:54 PM, David Antliff wrote: > Hello, > > I have a fairly simple fix I'd like to submit however it requires a > modification to an existing macports *patch* (as > found in the 'files' subdirectory of a Port). > > I've read the Contributors' Guide however it's not clear to me whether

How to contribute a patch to a macports patch

Hello, I have a fairly simple fix I'd like to submit however it requires a modification to an existing macports *patch* (as found in the 'files' subdirectory of a Port). I've read the Contributors' Guide however it's not clear to me whether I should create a new patch that patches the file twice

Re: Debian/Ubuntu-style -dev ports

On Friday May 20 2016 14:54:43 Thibaut Paumard wrote: Hi, > normal Linux user will never need, but the normal Macports user may need > this stuff, since the ports fall back to being built on the user machine > in a number of not-so-rare circumstance. Hence the idea of (semi-)automatic generation

Re: Debian/Ubuntu-style -dev ports

Le 19/05/2016 15:40, Ryan Schmidt a écrit : > But I haven't understood why splitting things the way Debian/Ubuntu do with > their -dev packages would be helpful to us in any way. Hi, It would have some usefulness, but also come with a load of trouble that the Debian/Ubuntu infrastructure allevia