public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE-4.1.3 + KDE-3.5.9 = messed up KDEDIRS ?
Date: Wed, 12 Nov 2008 22:11:35 +0100	[thread overview]
Message-ID: <200811122211.36029.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <200811121331.52699.dmitry@athabascau.ca>

On Mittwoch 12 November 2008, Dmitry S. Makovey wrote:
> On November 12, 2008, Volker Armin Hemmann wrote:
> > > I had something similar on my first try:
> > >
> > > kde-4 went into /usr
> > > kde-3 went into /usr/kde/3.5
> > >
> > > And bizarre weird errors kept happening. I remerged all of kde-4 with
> > > USE="kdeprefix" to put it back into /usr/kde/4.1 and all the weirdness
> > > went away
> >
> > in my opinion installing kde straight into /usr and changing the default
> > behaviour is the most stupid thing gentoo devs have done in the last
> > couple of years.
>
> wouldn't call it stupid though. FHS compliance is a good thing (I'm a
> sysadmin so I really appreciate when things can be easily located
> universaly). 

why? the FHS is a stupid standard. Why is following stupid standards a good 
thing? What next? LSB compliance - because it is great to be broken by 
definition?

> I think what failed is communication on that change. In
> developers defense I'd say that we're dealing with ~arch packages here so
> we've been warned they'll be somewhat not-so-stable. What I think needs to
> happen is gentoo users have to be warned in big red letters everywhere
> possible when upgrading from KDE3 to KDE4 to make firm decision whether to
> use "kdeprefix" or not.
>
it would have been better to NOT introduce that kdeprefix flag and instead 
introducing a FHS flag - which should have been off by default. The current 
way - kdeprefix to get sane behaviour, that turned off, changing the default 
behaviour is either stupid or evil.

> Enforcing proper FS layout is a good thing IMO. Just needs clear
> communication before marked as stable :)

Like making kde update interactive? Require a 'yes, I know about kdeprefix' 
dialog box?
kde has always been in its own directory tree. /opt back in the suse days for 
example. Elderly kde documentation told people to install kde in its own sub 
tree - and I loved that. I always hated gnome for cluttering /usr with its 
garbage. Having a big project like kde in its own tree has a bazillion of 
advantages. 





  parent reply	other threads:[~2008-11-12 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 16:31 [gentoo-user] KDE-4.1.3 + KDE-3.5.9 = messed up KDEDIRS ? Dmitry S. Makovey
2008-11-12 18:04 ` Peter Alfredsen
2008-11-12 18:52   ` Dmitry S. Makovey
2008-11-12 19:30 ` Alan McKinnon
2008-11-12 20:24   ` Volker Armin Hemmann
2008-11-12 20:31     ` Dmitry S. Makovey
2008-11-12 21:09       ` Alan McKinnon
2008-11-12 21:11       ` Volker Armin Hemmann [this message]
2008-11-12 21:47         ` Alan McKinnon
2008-11-12 22:33         ` Dmitry S. Makovey
2008-11-12 20:26   ` Dmitry S. Makovey

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=200811122211.36029.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --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