Re: This is how packaging should be done.
On Mon, 10 Jun 2002, Jeremiah Mahler wrote:
> What about the situation where a package is broken and the maintainer
> is unreachable. In the model described in the article anyone could
> fix the package (assuming it is not a critical package) but it would
> be marked as new so that people who only want safe packages would
> know to stay away from it. Then, if the maintainer comes back he/she
> could check the package and approve it so that it could now be used
> by people who want safe packages.
And that's what NMU are for. Everyone can prepare an NMU and ask for a
DD to upload it.
This approach has some advantages over the method you're describing. In
particular, a debian maintainer has to validate the package and perform
the upload. There's no need to add any kind of special information to tag
the package as "unsure, use at your own risk", since the maintainer is
trusted, and should, hopefully, check the package before pushing it to
the pool.
--
Emmanuel le Chevoir
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: