Le Samedi 1 Mars 2003 16:53, Buchan Milne a écrit :
> On Sat, 1 Mar 2003, Guillaume Rousse wrote:
> > I thought original club vocation was to port packages from cooker main
> > and contrib to current stable version. However, a quick look at the
> > MandrakeClub directory for 9.0 on mirrors shows they are actually many
> > packages there that are totally new: see enclosed list.
>
> Actually, both. If people in Mandrake Club request RPMs that are not
> currently packaged anywhere, a volunteer is supposed to package for
> Mandrake Club, have the requester/voters test it, and once he has some
> feedback, make it available for others, both via the "free" section (which
> goes to mandrake-devel mirrors) and hopefully to cooker contrib also(if
> applicable).
Allowing to introduce package directly at club level is plainly stupid 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.
> > I feel this is counter-intuitive, error-prone, and duplicated effort. Are
> > we supposed to port them in contrib now ?
>
> Preferably club-volunteers should do this, but feel free to jump in at
> this stage. I think Austin, Danny's and my packages are all in, plus
> Austin and I did most of thac's stuff. I will take a look at the list now.
>
> Porting to cooker has been mentioned on the club-volunteers list, but none
> of those with packages not in cooker replied.
Not a big surprise, considering lack of relationship between those two
different communities.
--
The speed with which components become obsolete is directly proportional to
the price of the component.
-- Murphy's Computer Laws n°9
