| Summary: | kile-1.1 emerges into wrong path | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andreas Waschbuesch <awaschb> |
| Component: | New packages | Assignee: | Dan Armak (RETIRED) <danarmak> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Andreas Waschbuesch
2002-08-19 12:40:23 UTC
This is correct. All our 3rd party (i.e. non-kde.org) kde apps install in /usr, and only the base kde distributions install in /usr/kde/$ver. Want details and reasons? yes please ... Well, shortly: - All other setups tied exhibited serious problems, this has no known issues. In other words it's our latest experiment :-) Seriously though, it's ok afaik. - This way, if ou have several KDE3 installed (say 3.0.x and 3.1.x and cvs), ou can run a 3rd party app (e.g. kile) from any of them, because it's installed in /usr and is equally accessible to all. When we installed it into the dir of one of the KDEs, the other KDEs had to include that dir in their path (and KDEDIRS) to be able to run it. That meant that they sometimes ran the components of the other KDE and not their own, which created problems. - This way is FHS-confirmant, the previous one was not. - Miscellania... Sounds reasonable - especially the misc :-) Seriously: I see - now with env.d and kde path setup ... even though I don't care too much about FHS and LFB. (That's what I like about gentoo most: You developers _explain_ Your thoughts even to the "just-testing" user.) Thanks! |
