Hi,
In theory, installing gtk3 has no impact and should be easy.
In practice, you will find that your compiler is a little out of date,
and things
like autoconf/etc wwon't work as expected. M4 may get in the way.
The default install location of gtk3 is on top of the existing
installation. How many
breakages are you prepared to put up with?
To get the gain of a time recording software (and the inherit
efficiencies) are you suggesting
that Steve risks a day of work to tidy up breakages? Surely not.
Steve is using that box to earn money. A day spent fixing things is not
a earning day.
The time was that I was interested in things like wasting days to get
the most efficient system.
That time has gone.
Derek.
On 30/05/14 14:55, Volker Kuhlmann wrote:
On Fri 30 May 2014 13:44:26 NZST +1200, Steve Holdoway wrote:
Because my workstation is exactly that, and is built with a close
approximation of the same packages to the servers I manage.
OK. Other ways to achieve that, this is one.
Sure it's
got a GUI - the standard CentOS GUI - but it also runs the same versions
of MySQL, nginx, PHP, Redis... as the servers I support.
The software in question required gtk3, ao I assume it's a desktop
application. How does installing a gtk3 library(!) on your desktop, for
the exclusive use of one desktop application, affect your mysql, php,
nginx, etc.? So far, your no-gtk3-on-my-desktop rule seems arbitrary and
nonsensical, so I'm interesting in your resoning (which so far I fail to
follow).
IMO bleeding edge has no place in the production environment.
That may be so, but your desktop is not a production environment. If you
need a proper staging server, install one. Virtualbox is good. Running a
stripped-down server as your desktop will give you headaches, as you're
noticing.
Volker
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
