Hi Yury,
On Sat, Aug 20, 2011 at 16:18, Yury G. Kudryashov
urkud.ur...@gmail.com wrote:
We have quite a few *.packages variables in NixOS: udev.packages,
hal.packages, dbus.packages etc.
I see only one reason for separating these packages from system.packages:
programs/config files/...
Another solution would be having a black/white list. If a package should
be added to DBUS but is contained in neither list tell the user to do
so. This way users have a choice but won't miss to make the decision.
Eg:
systemPackages = [ pkgProvidingDbusConfig pkg2ProvidingDbusConfig
cag1v4pdmutrs3kkovujrs8ntkvye6ky9q2wszvyoebw9tbb...@mail.gmail.com)
Mime-Version: 1.0
Content-type: text/plain; charset=UTF-8
Another solution would be having a black/white list. If a package should
be added to DBUS but is contained in neither list tell the user to do
so. This way users have a
you:
My system-path derivation lists more than 600 paths... I like this way
of managing package installation; your proposal would make it somewhat
harder...
Me:
[..] Eg we could add
additional info then:
meta / passthru = {
providesDbusConfig = {
why = Without this XY won't work
Hi!
We have quite a few *.packages variables in NixOS: udev.packages,
hal.packages, dbus.packages etc.
I see only one reason for separating these packages from system.packages:
programs/config files/... supplied by these packages are likely to be
executed/readed by a daemon running under root
Excerpts from Yury G. Kudryashov's message of Sat Aug 20 16:18:27 +0200 2011:
We have quite a few *.packages variables in NixOS: udev.packages,
hal.packages, dbus.packages etc.
I see only one reason for separating these packages from system.packages:
system.packages? Am I outdated or are
