On Tuesday 10 July 2001 21:33, Ken Thompson wrote:
> On Tuesday 10 July 2001 02:32 am, civileme wrote:
> > KIndly look at
> >
> > http://www.linuxbase.org/spec/
> >
> > We will be testing against this for next release.
> >
> > 8.0 made many problems. First, during its development, we had to
> > backport updates to 7.2, because Cooker was not available to 7.2 users
> > except those who broke their systems by installing glibc2.2.
> >
> > We took steps that this situation would not happen again by adopting a
> > policy for library naming and consequently changing packaging policy to
> > match, so new libraries could be added with impunity.
> >
> > Reiser fs was changed in kernel 2.4. If you install reiser for 2.4 you
> > may _not_ downgrade to the 2.2 kernel. I have a post on MandrakeForum
> > about how to install 2.2 kernel on 8.0 with Reiserfs
> >
> > http://www.mandrakeforum.com/article.php?sid=754&lang=en
> >
> > And this allows an upgrade later. So far, it appears that the Reiser
> > supplied with 2.2 is more stable by far and we came close to breaking the
> > kernel with all the patches to get the new reiser to work, nfs taking the
> > heavy hit.
> >
> > But I do see a lot of complaining about incompatibilities here and
> > elsewhere. Well , software grows and changes. The same folks complaining
> > about incompatibilities are often downloading tarballs or i386 rpms for
> > other distros to get packages that they can find with i586.mdk directly
> > in /contribs. Then, when asked, "Well, I wanted the latest version"
> > Then, when shown the latest version in cooker, "But that's untested!"
> > Well, where do they think we got the package to repackage for cooker?
> >
> > Anyway, we are advocates of standards. There are precisely two distros
> > where the menus are as identical as possible across window managers, and
> > ours is one of them. Of course some folks who develop desktops have
> > their own ideas about that and decided we "aren't a priority" though we
> > gave them all our info, so we lack the availability of a desktop that
> > wants to do things their way. Eventually, standards will be developed
> > for those things (there arlready are some, as in how Window managers
> > should communicate) and the issue will become a non-issue.
> >
> > Open standards can enhance development efforts and provide room for
> > creativity and for long-lived software. We hope to see those sorts of
> > standards adopted. As you will note in the link, there is a place to
> > post comments for the LSB.
> >
> > Civileme
>
> My question is, a while back we were advised NOT to use cooker packages,
> are we then able to use them in 8.0??????
There was a library incompatibility in 8.0 versus 7.2. Beginning with 8.0 we
have a library naming policy (which we hope becomes a standard) so you CAN ad
new versions of everything including glibc without breaking your system.
Currently Cooker is on the same libs, generally speaking, that work with 8.0,
but even if you need a new one, it is THERE and it CAN BE ADDED without
affecting your system. We wanted no repeats of the 7.2-8.0 hiatus, not ever.
Of course if a cooker package use turns you into a blue whale, don't expect
us to supply you with plankton and krill. :-)
Civileme
