[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Upgrading package openscenegraph

From: Mark Brand
Subject: Re: [Mingw-cross-env-list] Upgrading package openscenegraph
Date: Mon, 25 Apr 2011 22:06:42 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110221 SUSE/3.1.8 Thunderbird/3.1.8

Thanks a lot! I just performed some minor renamings:


However, it seems that our tutorial is no longer valid due to the
pkg-config related changes. Would you mind adjusting it?

     See doc/index.html, part "Step 5e: Cross compile your Project (OSG)"

I was wrong about the pkg-config patch being obsolete. The patch is now restored:


Step 5e is unchanged.

In the meantime, I upgraded all remaining packages. The only exceptions
are GD and POPT, because the sites libgd.org and rpm5.org are down. Of
course I added download mirrors, but it is still really strange that
those two sites are still down, and have been down for quite some time.
Usually, the downtime of a project lasts no longer than a few days ...

The downtime does seem rather unprecedented. Good idea to use the Debian and Slackware repos as mirrors.

Those two sites disturb our auto-upgrade helper. But I wanted to rework
that stuff anyway. In the future, we'll be able to circumvent such issues
via a "make -k update" or similar. BTW, do you make active use of
"make update", or "make update PKGS=...", or do you perform these steps
by hand?
I have to admit that I hadn't yet discovered the "PKGS=..." feature. When fishing for package updates, I often just removed the problem .mk files from src/.

  I'm just wondering because it seems that you cherry-pick the
packages you upgrade, while my "make update" is meant to be used to
upgrade as much as possible.

The impression of cherry-picking updates was probably created by my habit of focusing on updates to packages I know or use, or where the updates seem unlikely to break anything.

The updates I've "cherry-picked" are often ones I've found using "make update". In other cases I've become aware of updates via other channels.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]