civileme wrote:
>
> On Monday 25 December 2000 13:02, you wrote:
> > Civileme wrote:
> > > If it were that simple you would see it in /Mandrake-devel/unsupported
> > > where we put updates that do not qualify as critical or security.
> >
> > Is unsupported a response to reported bugs (same version but a higher
> > mdk patch level) or is it just a mandrake release of a a new
> > developer's version (version upgraded, mdk level set to 1, plus
> > still-relevant mdk patches) and compiled with and for the 7.2 gcc and
> > glibc?
> >
> > These must be specific to 7.2? If so it is very strange that there
> > is no /7.2/ in the path. What will happen when the incompatible 7.3
> > (if not onward compatible it should be 8.0, of course) has been
> > released? Answer: then you will need unsupported/7.2/i586/ and
> > unsupported/7.3/i586/.
> >
> > Or am I missing something?
Civileme,
> Yep you are.
It wasn't clear to me how, but thanks for the elucidation.
The same problem also must apply to /contrib. If a contrib binary
RPM is release sensitive then don't we need a path qualifier to
separate those contribs intended for 7.1 and 7.2 from those intended
for Cooker and what it will become later, 7.3?
--
Regards,
Ron. [AU]
