Le Samedi 1 Mars 2003 23:28, Steffen Barszus a �crit :
> > IMHO, and just contribute to global lack of coherency. Club people should
> > focus on porting, and forward new package request to contributers, so as
> > to keep one only package reference list, one only package policy, and one
> > only introduction procedure.
>
> So you mean:
> - requested packages have to go to cooker first and then rebuild for club
Yes
> - packages that don't appear to be possible for cooker shouldn't be
> uploaded to club (wether it is requested or not)
I forgot the club had no license restriction. However, i'm still convinced
those package should instead go in PLF, so as to keep a unique and
non-ambiguous introduction point.
I have no problems with the club mirroring and aggregating content from
different location, so as to sell this service to its users. What i disagree
is packages being introduced everywhere, making impossible to track them and
to propagate them to maximum extent in a rationale way.
--
When you finally buy enough memory, you will not have enough disk space.
-- Murphy's Computer Laws n�3
