Date: Sun, 4 Apr 2004 10:03:15 -0400 From: Craig Rodrigues <rodrigc@crodrigues.org> To: Sergey Matveychuk <sem@ciam.ru> Cc: freebsd-ports@freebsd.org Subject: Re: Problems with USE_AUTOMAKE_VER variable Message-ID: <20040404140315.GA41745@crodrigues.org> In-Reply-To: <406FFB70.8050206@ciam.ru> References: <20040404023418.GA37816@crodrigues.org> <20040404025156.GA29009@xor.obsecurity.org> <20040404030247.GA38436@crodrigues.org> <20040404033602.GA29488@xor.obsecurity.org> <20040404082956.GA39680@crodrigues.org> <20040404084107.GS75218@voodoo.oberon.net> <406FFB70.8050206@ciam.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 04, 2004 at 04:11:28PM +0400, Sergey Matveychuk wrote:
> Just ade makes a bad reputation for all commiters :(
Well everyone makes mistakes once in a while, and I make mistakes
too, so let's not single out ade@ for this.
My main complaint is the lack of keeping the port maintainer (me)
in the loop.
I am also disappointed by the slightly elitist attitude that
I am getting on the ports@ mailing list which is basically:
"We committers know better than you (port maintainer) what to do, and we
can make all sorts of commits to a port without keeping
the port maintainer informed because:
(1) these commits are minor, and we have a commit bit so we can do it
(2) it is too much work to send out an e-mail to the port maintainer,
because there are too many ports and too many e-mails to send out"
I don't have a problem with (1), but I feel that (2) is bogus. Keeping
port maintainers in the loop serves two purposes:
- politely keeps port maintainer informed about the status of a port
- educates port maintainer about the intricacies of the ports Makefile
system, and makes the person a better port maintainer
The only time I feel that sending out an e-mail is too much overhead
is if the MAINTAINER = ports@freebsd.org
If no one agrees with my points, then I am going to request two things:
-> If anybody commits anything to the devel/apr port, let me know via
e-mail, just as a matter of courtesy
(no matter how trivial the change)
-> Can someone add the following information to the Porters Handbook.
In order for a port maintainer to keep informed about potential
changes to a port:
-> Porters need to read /usr/ports/CHANGES regularly to keep up to
date with changes in the ports Makefile system.
-> Porters need to subscribe to freshports.org and add their
ports to the watch list.
The more of this stuff you guys can document for porters, the better.
--
Craig Rodrigues
http://crodrigues.org
rodrigc@crodrigues.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040404140315.GA41745>