From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Circular Block? kde-env / kdelibs
Date: Thu, 12 Oct 2006 12:00:24 +0200 [thread overview]
Message-ID: <200610121200.24738.alan@linuxholdings.co.za> (raw)
In-Reply-To: <200610112335.52534.bo.andresen@zlin.dk>
On Wednesday 11 October 2006 23:35, Bo Ørsted Andresen wrote:
> > [nomerge ] media-fonts/font-alias-1.0.1
> > [ebuild N ] kde-base/kde-env-3-r4
> >
> > This looks for me like font-alias wants to bring in kde-env ... but
> > might be a misinterpretation from my side as well since after that
> > I decided to migrate to KDE ~x86 and since then the depenency is
> > gone.
>
> ~khelpcenter-3.5.2 pulls in ~kdelibs-3.5.2 which pulls in kde-env.
> ~kdelibs-3.5.4 on the other hand blocks kde-env. The solution is to
> add kcontrol, kicker, khelpcenter (and any other packages that still
> require a downgrade of kdelibs) to /etc/portage/package.keywords...
A further point on this topic. kde-3.5.5 just went ~x86 and I've just
run into this blocker myself. For some reason I had kde-env in my
world, so I looked into the ebuilds to see what's going on. kde-env
does this:
RDEPEND="!>=kde-base/kdelibs-3.5.4-r2"
S=${WORKDIR}
src_install() {
dodir /etc/env.d
cat << EOF > ${D}/etc/env.d/99kde-env
KDEDIRS=/usr
CONFIG_PROTECT=/usr/share/config
#KDE_IS_PRELINKED=1
EOF
}
So it 1) blocks kdelibs-3.5.4-r2 and greater and 2)
creates /etc/env.d/99kde-env. So far so good.
The kdelibs blocker is because of this in kdelibs-3.5.5.ebuild function
src_install():
cat <<EOF > "${D}"/etc/env.d/45kdepaths-${SLOT} # number goes
down with version upgrade
PATH=${PREFIX}/bin
ROOTPATH=${PREFIX}/sbin:${PREFIX}/bin
LDPATH=${libdirs:1}
CONFIG_PROTECT="${PREFIX}/share/config ${PREFIX}/env
${PREFIX}/shutdown /usr/share/config"
KDEDIRS="${PREFIX}:/usr:/usr/local"
#KDE_IS_PRELINKED=1
EOF
so it writes it's own 45-kdepaths-3.5 which conflicts with the same
settings in kde-env. Fair enough and kdelibs-3.5.4-r2 is blocked for a
similar reason. But src_install() in kdelibs-3.5.4-r1 has only:
cat <<EOF > ${D}/etc/env.d/45kdepaths-${SLOT} # number goes down
with version upgrade
PATH=${PREFIX}/bin
ROOTPATH=${PREFIX}/sbin:${PREFIX}/bin
LDPATH=${libdirs:1}
CONFIG_PROTECT="${PREFIX}/share/config ${PREFIX}/env ${PREFIX}/shutdown"
EOF
No conflict with the settings from kde-env, so kde-env &
kdelibs-3.5.4-r1 work together. What's so special about
kdelibs-3.5.4-r2 and greater that they must supplant kde-env (apart
from the order the files are read in /etc/env.d)?
I can't decide if this is a bug or the devs are trying stuff out.
There's also NO bugs listed for kde-env on bugzilla, so I thought I'd
ask here first and get some comment
alan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-12 10:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 13:17 [gentoo-user] Circular Block? kde-env / kdelibs fire-eyes
2006-10-10 13:39 ` [gentoo-user] Circular Block? kde-env / kdelibs -- RESOLVED fire-eyes
2006-10-10 13:47 ` Neil Bothwick
2006-10-10 14:00 ` fire-eyes
2006-10-11 10:40 ` [gentoo-user] " Stefan Wimmer
2006-10-11 10:51 ` Bo Ørsted Andresen
2006-10-11 16:53 ` Stefan Wimmer
2006-10-11 21:35 ` Bo Ørsted Andresen
2006-10-12 9:45 ` Stefan Wimmer
2006-10-12 10:00 ` Alan McKinnon [this message]
2006-10-11 11:59 ` Neil Bothwick
2006-10-10 14:03 ` [gentoo-user] " Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610121200.24738.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox