Re: where do NEW packages go?
Adam Heath <email@example.com> writes:
> gcc 3.1 was released 2 *DAYS* ago. You can *NOT* honestly expect for things
> that depend on gcc 3.1 to suddenly be allowed in, so soon after a new
> package(and a MAJOR one at that) is released.
You're stating a reasonable rule here.
How would a maintainer go about finding out this rule? If they upload
such a package, will ftpmaster tell them? Or will it just get delayed
with no stated reason given?
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com