public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Werner <sebastian@werner-productions.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuilds for kde3 beta etc.
Date: Mon, 24 Dec 2001 13:11:29 +0100	[thread overview]
Message-ID: <2UVTONOMUPJHZ2X5DCYTTLFMLXVYW.3c271b71@wp> (raw)
In-Reply-To: <200112240959.fBO9x6YY085429@smtpzilla2.xs4all.nl>

Am 24.12.2001 10:59:02, schrieb Guido Bakker <guidob@gentoo.org>:

>
>That's why kde should install in its own directory... It's too big, just like 
>X11R6...

Yes, I agree. I would like to see kde in /opt/kde-${ver} or /usr/kde-${ver} like xfree.
The most libs that kde-use are kde-specific and will never have a function in other applications.
It's much easierer to manage multiple kde-version in full different trees...
and the system now to manually compile packages with:
KDEDIR=/usr/lib/kde-libs-${ver} ./configure --prefix=/usr
i very very ugly. Some packages of kde-apps search header files in /usr
not in $KDEDIR and then fail. I have created while do this with many apps some 
symlinks. But this is against the multi-version strategy

Regards

Sebastian Werner


>
>--
>Guido
>
>sön 2001-12-23 klockan 15.07 skrev Dan Armak:
>> On Sunday 23 December 2001 15:44, you wrote:
>> > That is why I'm against putting untested early-beta software in the
>> > packagesystem. Because no matter how much unsupported they are, we
>
>will
>
>> > always end up support it.
>>
>> Well, I don't think kde could break anything but kde apps. And I'm
>
>willing to
>
>> support the beta ebuilds.
>
>I wasn't talking about just KDE, but if we put KDE in I can't see why we
>couldn't put all alpha-releases. And others might break things. So can
>KDE3 if it installs over other files (like pilot-link installing over
>glibc and stuff).
>
>And what I'm talking about here is not that the actual code is beta
>(since very much of what is in portage now is "beta"). I'm talking about
>beta-releases (which are only meant for developers of KDE/GNOME/foo,
>depending on what kind of packages it is).
>
>> Of course I'd put up a 'don't use unless you know what you're doing'
>
>notice,
>
>> and mask them thoroughly. And support would be probably slower/more
>
>sparse,
>
>> but not necessarily so since I'll probably be using kde3 myself all
>
>the time
>
>> before long, and I know some other people will do so too before the
>
>final
>
>> release.
>
>Yes probably, and that is what frightens me.
>
>> As for problems that are rooted in kde3 as such (not just beta
>
>trouble), the
>
>> more input and testers the better - as long as they understand that
>
>it's not
>
>> *supposed* to be stable. As I've said, better solve these now than
>
>when
>
>> kde3-final comes out.
>
>Problems that come out of your ebuilds, yes, but really, if the tarballs
>used had been tested before being made available in Portage the job of
>finding errors in the ebuilds would be less.
>
>Regards,
>  Mikael Hallendal
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>





  reply	other threads:[~2001-12-24 12:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22 16:57 [gentoo-dev] ebuilds for kde3 beta etc Dan Armak
2001-12-22 17:28 ` Daniel Robbins
2001-12-22 18:00   ` Dan Armak
2001-12-22 18:29     ` Guido Bakker
2001-12-22 18:12       ` Dan Armak
2001-12-23 13:44         ` Mikael Hallendal
2001-12-23 14:07           ` Dan Armak
2001-12-23 23:08             ` Mikael Hallendal
2001-12-24  0:36               ` Daniel Robbins
2001-12-24  8:27               ` Geert Bevin
2001-12-25  1:12                 ` Mikael Hallendal
2001-12-25  5:00                   ` Dan Armak
2001-12-25  5:11                     ` Daniel Robbins
2001-12-25 12:10                       ` Mikael Hallendal
2001-12-25 15:49                         ` Daniel Robbins
2001-12-25 20:19                           ` Mikael Hallendal
2001-12-25 20:40                             ` Geert Bevin
2001-12-26  1:47                               ` Daniel Robbins
2001-12-26  2:14                                 ` Mikael Hallendal
2001-12-26  2:44                                   ` Daniel Robbins
2001-12-26  3:01                                     ` Mikael Hallendal
2001-12-26  3:33                                       ` Daniel Robbins
2001-12-26  4:10                                         ` Mikael Hallendal
2001-12-26  5:43                                           ` Daniel Robbins
2001-12-26  6:39                                             ` Dan Armak
2001-12-26  6:51                                               ` Mikael Hallendal
2001-12-26  6:56                                                 ` Joshua Pierre
2001-12-27 19:41                                               ` Damon M. Conway
2001-12-26  5:16                               ` Joshua Pierre
2001-12-26  1:51                             ` Daniel Robbins
2001-12-24  9:59               ` Guido Bakker
2001-12-24 12:11                 ` Sebastian Werner [this message]
2001-12-24 13:38                   ` Dan Armak
2001-12-25  1:14                   ` Mikael Hallendal
2001-12-23 14:13   ` Dan Armak
2001-12-26  9:34     ` Dan Armak
2001-12-26  9:37     ` Dan Armak
2001-12-26 13:46       ` Bart Verwilst
2001-12-26 16:50         ` Daniel Robbins

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=2UVTONOMUPJHZ2X5DCYTTLFMLXVYW.3c271b71@wp \
    --to=sebastian@werner-productions.de \
    --cc=gentoo-dev@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