u/d Newsletter/1003 by TimoSchoeler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

thus R P Herrold spake:
>>   Fetch the desired duplicity source code from 
>> https://code.launchpad.net/duplicity/, unpack it and change 
>> in its directory. There, just issue
>>
>> + {{{
>> - python setup.py install
>> + python setup.py install}}}
> 
> I see the above fragment in the draft newsletter, and frankly 
> am disappointed at proposed content not using the packaging 
> system.  It is clearly not a 'best practice'.  The item in 
> question will run as root, and one assumes will over time be 
> updated and have security fixes.
> 
> In a CentOS publication, we should not be proposing installing 
> time bombs that a later admin 'cannot see'.  We are all that 
> later admin as time packages and we forget the details of a 
> particular installation

Hi,

I absolutely agree with you; my 'plan' was to write it that way (in the
draft), and -- if my spare time allows -- build an appropriate RPM and
maybe even get it integrated in one of the repos. Then, I could modify
it to the 'decent way'.

As backup plan, I could just continue and use the not up-to-date
rpmforge package.

> -- Russ herrold

Timo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFLzwSGfg746kcGBOwRAga7AKCMGnJTpmcmihsP/FzqqNMZEu8CZgCgpaOQ
D1E02+qF8QF1b4qE3G65fMw=
=meG3
-----END PGP SIGNATURE-----


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Users]     [CentOS Virtualization]     [Linux Media]     [Asterisk]     [Netdev]     [X.org]     [Xfree86]     [Linux USB]     [Project Hail Cloud Computing]

  Powered by Linux