New port: NumlockX
Roman Neuhauser
neuhauser at bellavista.cz
Tue Sep 30 01:26:13 PDT 2003
# adamw at FreeBSD.org / 2003-09-29 18:59:45 -0400:
> >> (09.29.2003 @ 0646 PST): Jean-Baptiste Quenot said, in 0.9K: <<
> > I'm wondering why it always takes *ages* to change the ports tree.
> > Either the committers are not interested, or they don't have spare time
> > to handle such requests.
> >> end of "Re: New port: NumlockX" from Jean-Baptiste Quenot <<
>
> This is why:
> http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports&state=open&responsible=freebsd-ports-bugs
you're pointing at a problem and claiming that it's the cause of
the problem. the huge number of unassigned port PRs is IMO result
of FreeBSD having too few (active?) committers. the ports tree could
use a lot more autonomous maintainers who don't have to beg or wait
for long periods of time to have updates to their ports committed.
don't the FreeBSD hacks to cvs(1) allow for ACL granularity to the
directory level? (e. g. Alex Dupre could have commit in
/usr/ports/databases/mysql[[:digit:]]+-(server|client))
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
More information about the freebsd-ports
mailing list