[Nix-dev] Re: What about introducing security.packages?

[Marc Weber]

Hi Yury,

> > What exactly are you trying to do?
> My goal is to avoid the situation when someone adds a package to 
> dbus.packages but not to udev.packages.
Probably you're right that in most cases the defaults shipping with
packages get the job done (much more likely than omitting those rules).

first)
  What about

  pkg = mkDerivation {

    meta.provides = { # using attrs if there is ever need for some
                      # configuration you can add it easily. Also
                      # patching attrs is easier than adding/dropping
                      # items from lists?
      udevrules = true;
      dbussetup = true;
    }
  }

  Then overwriting those setting is even easier.

  Then we could introduce udev.packagesAutoAdd = true which picks
  packages from environment.systemPackages automatically based on the
  provides attr setting and it would be "opt-in" which some people will
  prefer.

second):
  You've seen that Eelco Dolstra is about implementing multiple
  outputs? So in the future packages may have:
  way:

  pkg.udevRules pkg.dubsSetup pkg.includes pkg.lib (or whatsoever, time
  will tell)

Marc Weber