On 02/23/2012 09:35 AM, Calvin Morrison wrote:
>> Really?
>>
>> trinity is not software locally installed by the local system admin?
> Right now it is - but very soon it will be installed from mirrors, via
> the package manager; users are expecting /usr/local to be stuff
> installed by them not the package manager
>
>> /usr/local IS for software installed after the base distribution.  Since
>> trinity is not installed by default in a lot of distros, onw should place
>> that sofware into /usr/local
> Just because it is not installed by default doesn't mean it shouldn't
> operate as a normal package.
>
>> What will you do when it is or how is distros supposed to pick it up if it
>> won't work when installed into /usr?
> That is for upstream to solve. as packagers we are just here to
> package. Trinity is continuing to work on the renaming effort - until
> it is finished I do not want any conflicts.
>
>> Installation into /usr _should_ be the goal not playing with installation
>> into /opt.
>>
>> Any way it's not an issue with me as I will continue on.....onward on my own
>> path installing into /usr/local, since it is your way or no way.
> I have offered many a time to have you join up and you consistently refuse.

No I don't refuse, since you folks are going in whatever way quite 
blindly and I don't wish to follow forces me to travel another path.
What I do works for me and if it can benifit others then good, use what 
I have.  It was you folks that refused to use what I have.
What you have just doesn't work for me or is horribly broken which 
does'nt help me at all.

>
>> /usr/local simplifes the install and keeps it separate from the distro stuff
>> (Arch soon to be my own scratch built ) and does not interfere with QT4 and
>> KDE4 and without all the mumbo jumbo associated with the install into /opt.
>>   The build goes better and the install goes better.
> Have you even bothered to read the arch package guidelines which so
> profess like a holy book?
>
> "Packages should never be installed to /usr/local"

That is from Arch linux vantage point.  ie from a distro point.
I am looking at it from a local system admin point which from the LSB 
points installation into /usr/local


>
> "/opt/{pkg}: Large self-contained packages such as Java, etc."
>
> I consider trinity a large self contained project.
>
> Furthermore /opt/ is a bit more of a saner solution because it helps
> keep everything seperate - this is something I think is good.
> especially while packages are still in beta stages.
>
> When the time comes to merge into the archlinux official packages, we
> can move it where they wish. I do think they will prefer /opt/
>
>

Where is KDE4 installed to on a arch linux install?

       cmake ../${pkgname}-${pkgver} \
                -DCMAKE_BUILD_TYPE=Release \
                -DCMAKE_SKIP_RPATH=ON \
                -DKDE_DISTRIBUTION_TEXT='Arch Linux' \
                -DCMAKE_INSTALL_PREFIX=/usr \
                -DSYSCONF_INSTALL_DIR=/etc \
                -DHTML_INSTALL_DIR=/usr/share/doc/kde/html \
                -DKDE_DEFAULT_HOME='.kde4' \
                -DWITH_FAM=OFF
        make

Oh look it installs into /usr just where tde should also install to .

The issue is that because of conflicts, tde can not be installed to /usr 
so the arch devs simply can not install it there.
Since it is _not_ installed from a distro... I believe that LSB states 
it is a locally installed package that should go into /usr/local.
After all it is local to the boxen in question.
I have kde-3.5.10 and tde 3.5.13 installed on a single slackware-12.2 
boxen with tde installed to /usr/local. Both easily work.

Any way I don't see arch picking up tde for a long time.