Re: [MiNT] mgw compile error

["Standa Opichal" <opichals@seznam.cz>]

Hi!

Ever heard of how to build a reasonably compatible RPM for any
OS/distribution
that supports that? Different virgin setup or chroot are the only way to go.

There were some changes in the mintlib. In case of such changes you would
probably want to keep the libraries and a whole .src.rpm repository tagged
so that it is possible to build the whole SpareMiNT with a single script
successfully. This was never true and I am pretty sure that there are
packages
that were not rebuild for more then 2 years. But it is good that you care
about your packages in this sense.

Best Reagards

STanda


-----Original Message-----
From: mint-bounce@lists.fishpool.fi [mailto:mint-bounce@lists.fishpool.fi]
On Behalf Of Martin Tarenskeen
Sent: Friday, September 23, 2005 4:11 PM
To: MiNT Mailing List
Subject: Re: [MiNT] mgw compile error

On Wed, 21 Sep 2005, Standa Opichal wrote:

> To compile up-to-date kernel you need up-to-date CVS version of mintlib.

OK. I understand.

But for me this creates a practical problem that I'd like to discuss here: 
I'm maintainer for a few simple RPM packages in the SpareMiNT repository. 
Once in a while I update these with newer versions. Now I don't want to
update the mintlib files in my include and lib directories with CVS
versions. I want to use the latest version that is available as stable
SpareMiNT rpm package. Packages in the SpareMiNT repository should be
buildable using libs that are available in that same repository.

And having two different mintlibs on my system is something I'm not looking
forward to. Big changes in mintlib only occur once in a while but certainly
not every day. Maybe mintlib package in SpareMiNT should be updated after
every small but important change.

That would help me anyway.

Same story for gemlib and cflib.

-- 

Martin Tarenskeen