On Thu, Oct 24, 2002 at 10:16:00AM +0200, Warly wrote:
> 
> I do think it is idiot not allowing to some contributors that want to support
> their packages to do it.

I am glad somebody sees my point.  :-)

> However it is obviously touchy it this seems to be part of Mandrake official
> support policy.

Well, part of the problem is that contrib doesn't have any structure.
i.e. what version of Mandrake Linux is contrib applicable to?
Current (i.e. 9.0 as of this time) only?  Cooker only?  If contrib is
built and periodically maintained against Cooker, it becomes useless
(if there are lib changes in Cooker) for even the current released
Mandrake Linux.

Is Contrib "frozen" when Cooker becomes a release as it did when 9.0
was released?  i.e. will new additions/updates to Contrib be put into
a "Cooker contrib" dir or do they go into the dir that was/is used
for 9.0?

If contrib is frozen when a release is made, perhaps a contrib/updates
for the 9.0 frozen contribs can be made.

> At present the "unsupported" directory will quite fit to these goal. However
> it is right now quite messy.

I don't think I have even seen unsupported.  What is the difference
between unsupported and contrib?

> - either to create a sub dir call updates in the unsupported directory, that
> will contains the updates made by contributors or mandrakiens for security
> fixeson unsupported packges.

OK.

> This will be done alongside with a 9.0 and maybe 8.2 compilation environment
> on the contributors compilation machine and adequate upload scripts.

Or maybe, to foster an environment rich with RPMs, Mandrake can set up
a machine (or simply some chroots or UMLs on an existing machine)
which simply takes a contributed SRPM (ftped to a directory for
instance) and automagically (i.e. hands-off so it's not a Mandrake
headache) builds it for both a Cooker contribs and a "current release"
contribs.  A build report can be made publicly available so that
errors in building SRPMs can be checked by maintainers and corrected.

b.

-- 
Brian J. Murrell

Attachment: msg79609/pgp00000.pgp
Description: PGP signature

Reply via email to