[MacPorts] #26646: Qt 4.7 Release
MacPorts
noreply at macports.org
Thu Oct 14 07:22:32 PDT 2010
#26646: Qt 4.7 Release
----------------------------------+-----------------------------------------
Reporter: eric.c.brown@… | Owner: michaelld@…
Type: update | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: | Port: qt4-mac, qt4-x11, qt4-mac-devel, qt4-x11-devel
----------------------------------+-----------------------------------------
Comment(by michaelld@…):
Before I was a MP developer, I also posted straight-up Portfiles
sometimes. I was told to post diffs instead, and I had the same reaction
as you do: it is -just- a relatively simple 5 step process to get the
diffs, so what's the big deal? What you write is true all around, but you
are not thinking of how busy we as MP developer are -- not just with MP
but with the rest of our lives; I, at least, volunteer my time and effort
to make MP a better system and product (I assume most other MP developers
do too). Given the number of Portfiles and tickets I work with, taking
the 2-3 minutes to check out someone else's changes via the 5 steps
-really- adds up. I'd rather complain for 2-3 minutes once than to have
to check out all of the non-diff Portfiles.
OTOH, if you & everyone else post just a diff, anyone can quickly view it
and see what you changed and if it's worth further attention -- a simple,
quick 1 step process on -our- part. Just about anyone who understands how
to manipulate a Portfile can do "patch -p0 < ~/Downloads/patch-foo-
Portfile.diff" just as easily as "mv ~/Downloads/foo-Portfile ./Portfile".
Yes, it takes another step on -your- part to do the diff, but it makes
everyone else's life easier when we just just a simple diff to work with.
As for your second point (that it's not for me): Maybe so, but I'm the
owner of this ticket and port, so, yes, it is for me too.
Think about it, please. I'm not trying to be argumentative or
disrespectful, just pragmatic given my almost-never ending work-queue &
knowing that other MP developers are in a similar situation.
--
Ticket URL: <https://trac.macports.org/ticket/26646#comment:13>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list