On 15/05/2006 05:16, Roy Schestowitz spake thusly:
> __/ [ [H]omer ] on Sunday 14 May 2006 21:05 \__
>> On 14/05/2006 19:59, rapskat spake thusly:
>>> I found this nifty bit of software called kinstaller
>> 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
>> difficult.
> 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.
Well I'm a Fedora guy and very security conscious. FC4 and 5 implement
SELinux, which I always run in *strict* mode. Administering policies for
binaries in users' $HOME directories would be a nightmare, and IMHO,
with or without SELinux, and inherent security risk.
Certainly there would be little need for resource and dependency
tracking, particularly if the binaries were static, but even in a closed
system with only one user, I just don't like the idea, and AFAICT it is
definitely *not* FHS compliant, something about which I am a bit pedantic:
http://www.pathname.com/fhs/pub/fhs-2.3.html#HOMEUSERHOMEDIRECTORIES
--
K.
/* values of ß will give rise to dom! */
Fedora Core release 4 (Stentz) on sky, running kernel 2.6.16-1.2108_FC4
06:52:53 up 2 days, 15:43, 3 users, load average: 0.02, 0.03, 0.00
|
|
