Re: [gentoo-user] kde path is missing
Op dinsdag 28 juni 2005 23:45, schreef Zac Medico: snip Do you guys have USE=-arts by any chance? $ equery belongs /etc/env.d/46kdepaths-3.4 kde-base/arts-3.4.1-r2 $ cat /etc/env.d/46kdepaths-3.4 PATH=/usr/kde/3.4/bin ROOTPATH=/usr/kde/3.4/sbin:/usr/kde/3.4/bin LDPATH=/usr/kde/3.4/lib CONFIG_PROTECT=/usr/kde/3.4/share/config /usr/kde/3.4/env /usr/kde/3.4/shutdown Zac Yes, that's it. Now I wonder, why are those paths included in the package arts, and not in kde-env, which seems more logical to me? Jan -- If it ain't broken, you just haven't looked hard enough. Fix it anyway. -- Tom Peters pgpVDB4h0yrkn.pgp Description: PGP signature
Re: [gentoo-user] kde path is missing
Jan Callewaert wrote: Hi, I was recompiling kde today, but now the path isn't set anymore. If I run env-update, the bin directory of kde isn't added to the path (of course after executing source /etc/profile). My kde-env looks like this: # cat /etc/env.d/99kde-env KDEDIRS=/usr CONFIG_PROTECT=/usr/share/config KDE_MALLOC=1 #KDE_IS_PRELINKED=1 which is like you'd expect from the ebuild kde-env. I find it strange that there is no PATH variable in it for kde. I can manually add ROOTPATH=/usr/kde/3.4/bin to the env file, and then /etc/profile.env gets updated, and also the path. But I wonder what's the correct way to do this is, since I'll have to update it each time I install a new kde. Regards, Jan Wow man... that's true. It happens to me too. Maybe we can change it to /usr/kde/3.4, right? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kde path is missing
Op dinsdag 28 juni 2005 17:10, schreef Jan Callewaert: Hi, I was recompiling kde today, but now the path isn't set anymore. If I run env-update, the bin directory of kde isn't added to the path (of course after executing source /etc/profile). My kde-env looks like this: # cat /etc/env.d/99kde-env KDEDIRS=/usr CONFIG_PROTECT=/usr/share/config KDE_MALLOC=1 #KDE_IS_PRELINKED=1 which is like you'd expect from the ebuild kde-env. I find it strange that there is no PATH variable in it for kde. I can manually add ROOTPATH=/usr/kde/3.4/bin to the env file, and then /etc/profile.env gets updated, and also the path. But I wonder what's the correct way to do this is, since I'll have to update it each time I install a new kde. Regards, Jan and for a regular user to work, I have to set PATH also off course. Jan -- If it ain't broken, you just haven't looked hard enough. Fix it anyway. -- Tom Peters pgpUGloFiOHdQ.pgp Description: PGP signature
Re: [gentoo-user] kde path is missing
Op dinsdag 28 juni 2005 17:42, schreef Rafael Fernández López: Jan Callewaert wrote: Hi, I was recompiling kde today, but now the path isn't set anymore. If I run env-update, the bin directory of kde isn't added to the path (of course after executing source /etc/profile). My kde-env looks like this: # cat /etc/env.d/99kde-env KDEDIRS=/usr CONFIG_PROTECT=/usr/share/config KDE_MALLOC=1 #KDE_IS_PRELINKED=1 which is like you'd expect from the ebuild kde-env. I find it strange that there is no PATH variable in it for kde. I can manually add ROOTPATH=/usr/kde/3.4/bin to the env file, and then /etc/profile.env gets updated, and also the path. But I wonder what's the correct way to do this is, since I'll have to update it each time I install a new kde. Regards, Jan Wow man... that's true. It happens to me too. Maybe we can change it to /usr/kde/3.4, right? No, it should point directly to the bin directory. Otherwise the binaries are not found. -- If it ain't broken, you just haven't looked hard enough. Fix it anyway. -- Tom Peters pgp90A9iQIu44.pgp Description: PGP signature
Re: [gentoo-user] kde path is missing
Jan Callewaert wrote: Op dinsdag 28 juni 2005 17:42, schreef Rafael Fernández López: Jan Callewaert wrote: Hi, I was recompiling kde today, but now the path isn't set anymore. If I run env-update, the bin directory of kde isn't added to the path (of course after executing source /etc/profile). My kde-env looks like this: # cat /etc/env.d/99kde-env KDEDIRS=/usr CONFIG_PROTECT=/usr/share/config KDE_MALLOC=1 #KDE_IS_PRELINKED=1 which is like you'd expect from the ebuild kde-env. I find it strange that there is no PATH variable in it for kde. I can manually add ROOTPATH=/usr/kde/3.4/bin to the env file, and then /etc/profile.env gets updated, and also the path. But I wonder what's the correct way to do this is, since I'll have to update it each time I install a new kde. Regards, Jan Wow man... that's true. It happens to me too. Maybe we can change it to /usr/kde/3.4, right? No, it should point directly to the bin directory. Otherwise the binaries are not found. Do you guys have USE=-arts by any chance? $ equery belongs /etc/env.d/46kdepaths-3.4 kde-base/arts-3.4.1-r2 $ cat /etc/env.d/46kdepaths-3.4 PATH=/usr/kde/3.4/bin ROOTPATH=/usr/kde/3.4/sbin:/usr/kde/3.4/bin LDPATH=/usr/kde/3.4/lib CONFIG_PROTECT=/usr/kde/3.4/share/config /usr/kde/3.4/env /usr/kde/3.4/shutdown Zac -- gentoo-user@gentoo.org mailing list
