Linked by Thom Holwerda on Tue 24th Jul 2007 00:21 UTC
Thread beginning with comment 258010
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: release synchronization
by anda_skoa on Wed 25th Jul 2007 11:47
in reply to "RE[3]: release synchronization"
when i recently tried to install some stuff for kde i encountered that one had to set a compile time option pointing to where the base directory of kde was.
This is an option, though I would not suggest doing it this way, since it will write locally compiled files into the location controlled by the package manager.
Usually it is easier to just use the default prefix (/usr/local) and extend $KDEDIRS to include it.
This often has has the additional advantage of /usr/local being writable by a non-root group (e.g. "staff") and thus not requiring root access to install local software.
RE[5]: release synchronization
by hobgoblin on Wed 25th Jul 2007 19:43
in reply to "RE[4]: release synchronization"
RE[4]: release synchronization
by lemur2 on Thu 26th Jul 2007 06:57
in reply to "RE[3]: release synchronization"
then there is ever so slight variations in where files go. when i recently tried to install some stuff for kde i encountered that one had to set a compile time option pointing to where the base directory of kde was. this because some distros, like debian, put it in /opt/kde, while others put them under /usr.
this, and having rpm, deb, and maybe a host of other variants makes it a nightmare to maintain intallers.
this, and having rpm, deb, and maybe a host of other variants makes it a nightmare to maintain intallers.
Why?
Just pick a distribution and stick to it.
Pick a distribution with a large community (Ubuntu, Debian or Fedora) and someone else will have already compiled it for you before you even finish your source code download.
If you are a developer ... then this wont be a problem either. Set up a few different compiler environments (Ubuntu, Debian and Fedora) and compile your app once for each one.
RE[5]: release synchronization
by hobgoblin on Thu 26th Jul 2007 13:52
in reply to "RE[4]: release synchronization"
if one could have a single compile environment that would spit out different packages for different use. or some kind of meta-package that could morph to fit into different packaging system, maybe.
but the more complexity or variations one add to something, the less likely it is that anyone will bother.







Member since:
2005-07-06
the issue is more that on windows or mac, the app and whatever third party libs it use, come as a bundle.
this can be both a blessing and a curse. i recall microsoft finding a problem in one of their base libs. but the only real fix they could provide was some patches for their own products, and a program to sniff out other copies of the lib in the folders of the individual third party apps.
but from a usability standpoint, having one stop downloads of software from places like filehippo, snapfiles, download.com or the classical tucows, makes it simpler for third party developers to just toss the program up there and hope someone finds use for it.
then there is ever so slight variations in where files go. when i recently tried to install some stuff for kde i encountered that one had to set a compile time option pointing to where the base directory of kde was. this because some distros, like debian, put it in /opt/kde, while others put them under /usr.
this, and having rpm, deb, and maybe a host of other variants makes it a nightmare to maintain intallers.
thank god that i choose to use gobolinux, where i can go makerecipe on a url to the sourcecode tar-ball if there isnt one up on the recipe store, and 9 times out of 10 it will install neatly in its own versioned sub-dir under /programs.
if one is lucky one can even invoke newversion when a more recent version then the one the recipe store have available shows up, and the old one will be used as a basis to make a new recipe.
and if one wants to make a binary package. go createpackage after the compile. this basically tar-balls the versioned subfolder and thats it
mind you, the current gui available for managing all this, manager, is dreadful. i wonder if i should read up on python and see if i can rework it.