Sorry for not replying earlier, I had a lot of work to do.
We had the discussion about extra fork for ports on the FreeBSD forums too
(few days ago) and they suggested redports. I didn't know before that such
a thing already existed, so it's okay. I apologize for not reasearching the
matter more thoroughly before.
The arguments that John presented are sound and good. I understand now, why
you don't want to officially endorse such an idea. I will give reports a
chance and see what goes.
In any case, thanks for the replies!
Jo?e
2013/6/13 Julian H. Stacey <jhs at berklix.com>
> Hi, Reference:
> > From: =?ISO-8859-2?Q?Jo=BEe_Zobec?= <jozze.zepl at
gmail.com>
> > Date: Wed, 12 Jun 2013 20:04:30 +0200
>
> > Apart from the maintainer of the port, there would also be
"sub"
> > maintainerswhich would be those people who helped patch the port into
the
> > good shape:
> >
> > # make -C /usr/ports/section/someport maintainer
> >
> > would return the maintainer (1st address) and additional addresses to
> turn
> > for questions. When the port would be committed to the
"good" ports tree,
> > sub-maintainers would be left out.
>
> Maybe it'd help to break jozze.zepl's suggestions in to 2 parts ?
> - Working & non working ports tree
> (No comment from me on that)
>
> - Multiple maintainers
>
> I believe MAINTAINER= value is currently a unitary mail address, which
> is [usually] an individual or a freebsd mail list.
> I recall before we've discussed adding names of alternates/ extras,
> (perhaps comma seperated), & that some who maintain
> .mk macros & shell scripts pointed out some difficulties if changed.
>
> Even within the current unchanged syntax,
> handfulls of maintainers might already co-operate on a per port basis,
> with eg
> MAINTAINER=port_xyz_maintainers at their-domain.com
>
> their-domain.com /etc/mail/aliases:
> port_xyz_maintainers: port_xyz_maint0, port_xyz_maint1
> port_xyz_maint0: jack at upthehill.com
> port_xyz_maint1: jill at downthehill.com
>
> Cheers,
> Julian
> --
> Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich
> http://berklix.com
> Reply below not above, like a play script. Indent old text with
"> ".
> Send plain text. No quoted-printable, HTML, base64,
> multipart/alternative.
>