__/ [ [H]omer ] on Sunday 14 May 2006 21:05 \__
> On 14/05/2006 19:59, rapskat spake thusly:
>> I'm all about simple and easy. Hassle free is my motto, being the
>> lazy person I am.
>> So when I found this nifty bit of software called kinstaller, I was
>> thrilled! Basically, it does all of the steps required for
>> extracting, compiling and installing a source tarball package and
>> reduces it to a few mouse clicks. That's nice!
>> Happy compiling :-)
> Note however, that it doesn't create resource trackable packages like
> RPM. I used to use CheckInstall, which *does* create RPMs from tarballs,
> but since starting with Fedora, I find it just as easy to create spec
> files and package the applications myself.
> I'd still recommend CheckInstall for ordinary users, however, since
> having loose-canon binaries on your system, will make maintenance
Very true, [H]omer. I always enjoy reading your insight on such matters.
Sticking to the point, what I _personally_ tend to do, for the sake of
maintenance, as well as ease in migration, is store source and/or package
in my home directory. This tends to prevent a clutters of binaries,
wherein both your 'own' programs and the distribution's default programs
sort of mingle.
On a machine that accommodates just one or two users, it may deem fairly
acceptable. Not consuming too much space; not hindering updates and
distributability. For what it's worth, rather than add the binaries to
somewhere among the PATHDEF, I just set up keyboard accelerators using
xbindkeys. The "~/" syntax makes it very 'portable'. I also have a special
affinity for JRE programs because they are highly portable and
well-encapsulated. Thumbs up to Java, but provided you have strong
hardware and plenty of resources to spare. It's a trade-off.
Roy S. Schestowitz | "Signature pending approval"
http://Schestowitz.com | SuSE Linux ¦ PGP-Key: 0x74572E8E
5:05am up 17 days 12:02, 11 users, load average: 0.05, 0.49, 0.92
http://iuron.com - Open Source knowledge engine project