Editing maintained ports
jmr at macports.org
Wed Jan 7 06:08:30 PST 2015
On 2015-1-8 00:09 , Mojca Miklavec wrote:
> On Tue, Jan 6, 2015 at 12:14 PM, Ryan Schmidt wrote:
>> Existing source files, including Portfiles, containing tabs should have them converted to spaces, and have the modeline added declaring that.
>> You can do this to ports you maintain, or ports which are unmaintained. For maintained ports, whether openmaintainer or not, you should get consent from the maintainer first.
>> Maintainers should proactively make this change in all their ports without needing to be asked.
> OK, sure, but what if maintainers don't do the change?
Tabs or spaces in portfiles is the maintainer's choice, as documented in
> For those remaining hundred ports it would be nice to:
> a) clean up the whitespace
> b) upgrade the version
> c) add 5.18 5.20 to supported versions
> d) do any other clean-up, changes or testing that might be needed
> What's the proper way to get this done without violating the rules? In
> particular: should one open one hundred tickets asking for permission
> to change whitespace for every single port? This is painful mostly
> because there usually need to be done multiple changes simultaneously
> (whitespace + upgrade + support for 5.18/5.20; so probably three
> patches with a request: change whitespace, upgrade on original port,
> upgrade on the port with whitespace adjustments) and opening one
> hundred tickets just multiplies the work. Let alone the fact that
> probably 90% of those requests wouldn't even be answered.
If there is no response to tickets, you can initiate the port abandoned
procedure. But you shouldn't open 100 tickets asking to change whitespace.
More information about the macports-dev