From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Multiple kdelibs
Date: Sun Oct 21 14:54:02 2001 [thread overview]
Message-ID: <1003697689.9273.1.camel@zoidberg> (raw)
In-Reply-To: <0GLK00823ON0GB@mxout2.netvision.net.il>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
sön 2001-10-21 klockan 22.21 skrev Dan Armak:
> There are several options imo (in no particular order):
> 1. Develop a scheme for kdelibs similar to that used with qt. Place different
> kdelibs in /usr/lib/kdelibs-$V and juggle paths around. Use eclasses to
> ensure correct kdelibs is used.
> Pro: easy to set up, unless unexpected problem emerges.
> Con: there's not much sense in having mutliple kdelibs like this unless we go
> for option 2.
> This is FHS0compatible, but probably falls under some "in the last extreme"
> clause.
Why can't you have them in /usr/lib/kdelibs-$V (just another dir than
/opt/kde$V).
But isn't it just the header-files that is the problem? And not the libs
(or do the libs cause troubles too?)
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-21 20:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 14:24 [gentoo-dev] Multiple kdelibs Dan Armak
2001-10-21 14:54 ` Mikael Hallendal [this message]
2001-10-22 14:08 ` Dan Armak
2001-10-22 14:13 ` Mikael Hallendal
2001-10-22 14:21 ` Dan Armak
2001-10-22 14:42 ` Mikael Hallendal
2001-10-22 15:13 ` Dan Armak
2001-10-22 16:40 ` Mikael Hallendal
2001-10-22 17:56 ` Nathaniel Grady
2001-10-22 18:39 ` Mikael Hallendal
2001-10-22 23:03 ` Dan Armak
2001-10-23 3:42 ` Mikael Hallendal
2001-10-23 13:45 ` Dan Armak
2001-10-23 14:17 ` Martin Schlemmer
2001-10-23 16:35 ` Mikael Hallendal
2001-10-24 3:11 ` Dan Armak
2001-10-22 23:03 ` Dan Armak
2001-10-22 23:01 ` Dan Armak
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=1003697689.9273.1.camel@zoidberg \
--to=hallski@gentoo.org \
--cc=gentoo-dev@cvs.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