On Wednesday 26 September 2012 10:42:07 Jonathan Marten wrote:
> After a lot of discussion, is seems that there are some executables
> (as per Thiago's list) that can be moved out. For others
> (e.g. Akonadi) it is problematic because there is no standardization
> on the location for a "system-wid
Am 20.09.2012 17:53, schrieb Thiago Macieira:
On quinta-feira, 20 de setembro de 2012 16.50.57, Ralf Habacker wrote:
kdeinit4
used on windows, need to stay
Used by people? Or used by programs and scripts?
used by people. On windows there are a few more options intended for
command line use
After a lot of discussion, is seems that there are some executables
(as per Thiago's list) that can be moved out. For others
(e.g. Akonadi) it is problematic because there is no standardization
on the location for a "system-wide" libexec as per David's comments
below, so they will have to stay unl
On 2012-09-20, David Faure wrote:
> We really need a FHS addition for libexec.
not really. the libexec executables is in general a implementation
detail of the given library.
We have the rare case in KDE that we actually call other libraries'
executables, which is a different thing, and one I ha
On 09/20/2012 11:53 AM, Thiago Macieira wrote:
> On quinta-feira, 20 de setembro de 2012 16.50.57, Ralf Habacker wrote:
> kdeinit4
>>
>> used on windows, need to stay
>
> Used by people? Or used by programs and scripts?
>
> If it's the latter, it can be moved.
>
The only reason I've ever ru
Hello all. Sorry for messing around here (I'm not a KDE developer) but in
case anyone interested in OpenBSD look, I'll try to present it here via
some thoughts and facts.
1. OpenBSD doesn't care about FHS, and all *nix except Linux distros do not
care either. Because FHS is Linux-only itself.
2.
>kdeinit4
used on windows, need to stay
David Faure wrote:
> On Thursday 20 September 2012 19:36:39 Sune Vuorela wrote:
>> On 2012-09-20, Kevin Krammer wrote:
>>> Do you mean $PREFIX/libexec, where $PREFIX will often be /usr (for=20
>>> distribution packages)?
>>
>> that only works in redhat/fedora land. In other distributiotns, like
>>
On Thursday 20 September 2012 19:36:39 Sune Vuorela wrote:
> On 2012-09-20, Kevin Krammer wrote:
> > Do you mean $PREFIX/libexec, where $PREFIX will often be /usr (for=20
> > distribution packages)?
>
> that only works in redhat/fedora land. In other distributiotns, like
> debian and ubuntu, libe
On 2012-09-20, Kevin Krammer wrote:
> Do you mean $PREFIX/libexec, where $PREFIX will often be /usr (for=20
> distribution packages)?
that only works in redhat/fedora land. In other distributiotns, like
debian and ubuntu, libexec is placed in directories under
prefix/libdir/libraryname/ - e.g.
Kevin Krammer writes:
> Do you mean $PREFIX/libexec, where $PREFIX will often be /usr (for
> distribution packages)?
Yes, that's what I meant - in theory equivalent, since $KDEDIR will be
set to the same at runtime.
--
Jonathan Marten http://www.keelhaul.demon.co.uk
Twi
On quinta-feira, 20 de setembro de 2012 16.50.57, Ralf Habacker wrote:
> >> >kdeinit4
>
> used on windows, need to stay
Used by people? Or used by programs and scripts?
If it's the latter, it can be moved.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architec
On Thursday, 2012-09-20, Jonathan Marten wrote:
> Kevin Krammer writes:
> > Agreed. It is important, however, to remember that some of those (e.g.
> > akonadiserver, akonadi_control) are not KDE programs and can therefore
> > not be in a KDE specific libexec location but have to go into a standard
Kevin Krammer writes:
> Agreed. It is important, however, to remember that some of those (e.g.
> akonadiserver, akonadi_control) are not KDE programs and can therefore not be
> in a KDE specific libexec location but have to go into a standard (FHS or
> freedesktop.org) location for that purpose
On 2012-09-20, Kevin Krammer wrote:
> Agreed. It is important, however, to remember that some of those (e.g.=20
> akonadiserver, akonadi_control) are not KDE programs and can therefore not =
> be=20
> in a KDE specific libexec location but have to go into a standard (FHS or=20
> freedesktop.org) l
On Thursday, 2012-09-20, Thiago Macieira wrote:
> On quinta-feira, 20 de setembro de 2012 12.46.47, Jonathan Marten wrote:
> > There are a lot of executables in $KDEDIR/bin which are used for
> > internal purposes within KDE and are not intended to be directly
> > executed by the end user. Having
On quinta-feira, 20 de setembro de 2012 12.46.47, Jonathan Marten wrote:
> There are a lot of executables in $KDEDIR/bin which are used for
> internal purposes within KDE and are not intended to be directly
> executed by the end user. Having these in the user's $PATH is not
> necessary and has ove
There are a lot of executables in $KDEDIR/bin which are used for
internal purposes within KDE and are not intended to be directly
executed by the end user. Having these in the user's $PATH is not
necessary and has overheads for the shell (and for the user, when
doing tab-completion of a command).
18 matches
Mail list logo
