Package: cfengine2
Version: 2.1.20-1
Severity: wishlist

There used to be (at least in woody, sarge) an automatic class
"debian_3_0" and "debian_3_1" in the versions of cfengine shipped
with woody and sarge. The version in sarge even had its class defined
long before it was released. This is very helpful in a mixed-debian
environment. Current etch version does not have this feature.

In addition, I suggest that you use classes like debian_sid,
debian_etch, debian_sarge in the future, since these can be defined at
all times - unlike debian_version_number, which is not always defined
for testing and never is for sid.

Now that I'm at it, I'd suggest to define the plain kernel version, as
well. That is, 2.6.8, with no -1-686 etc. It would also be helpful
since some things change between kernel versions but not between
kernel architechtures or recompilations. This is especially useful in
our environment where some servers simply cannot be upgraded
immediately if the upgrade is not critical.

-Juha

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-amd64-k8-smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages cfengine2 depends on:
ii  debconf [debconf-2.0]        1.5.2       Debian configuration management sy
ii  debianutils                  2.16.2      Miscellaneous utilities specific t
ii  libc6                        2.3.6-15    GNU C Library: Shared libraries
ii  libdb4.2                     4.2.52-23.1 Berkeley v4.2 Database Libraries [
ii  libssl0.9.8                  0.9.8b-2    SSL shared libraries
ii  perl                         5.8.8-4     Larry Wall's Practical Extraction 

cfengine2 recommends no packages.

-- debconf information:
* cfengine2/run_cfservd: false
* cfengine2/run_cfexecd: false
* cfengine2/run_cfenvd: false


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to