Source Mage code commit list

[Arwed von Merkatz <v.merkatz AT gmx.net>]

On Thu, May 11, 2006 at 08:52:27AM -0700, Eric Sandall wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> seth AT swoolley.homeip.net wrote:
> > On Thu, May 11, 2006 at 01:04:50AM +0200, Andra?? ruskie Levstik wrote:
[...]
> >> How about if we provide the same thing we provide for the nano spell...
> >>
> >> A list of possible rulesets to install ragning from:
> >> sane-minimal-default to a full-blown-do-all-the-magic
> >>
> >> And simply let the user decide which one they want...
> > 
> > That's not really talking about defaulting then.  That's about its 
> > converse,
> > what to add later.
> > 
> > A sane _default_ to me is defined by the interplay between udev and our 
> > spells.
> > 
> > Spells that require a specific device name should work with udev's 
> > defaults, whether that involves modifying the spell to use our udev 
> > default or modifying udev to add an alias/move devices, I don't care so 
> > much as long as it works, is somewhat consistent, and we give somebody 
> > reasonable interpretive power over this decision (the maintainer, 
> > probably).
> > 
> > I just want stuff to work by default.  While subdepends would work here, 
> > it's too intrusive to rebuild your udev just for a minor file somewhere 
> > else.  Perhaps a udev.d sourcing directory with a cluster of spells that 
> > provide custom rulesets (with conflicts among each other if needed) is 
> > what makes sense if a rule is needed by many spells.
> 
> If the sourcing of udev.d is possible that would be preferred, IMO.
> Since then packages can add/remove their rules as needed without
> fiddling with udev itself (much as we have packages install their own
> init.d/xinetd.d/profile.d/etc. scripts).
 
That's already how it's done. All files in /etc/udev/rules.d ending in
.rules get used by udev. The question is what spell should provide what.
The cd writer permissions are already done in the cdrtools/dvdrtools
spells, same for a couple others. Alsa rules could probably go to the
alsa-lib spell. But there's the whole module autoloading stuff and base
devices like console, tty*, rtc, ... that have to be setup somewhere.

-- 
Arwed v. Merkatz                              Source Mage GNU/Linux developer
                                                    http://www.sourcemage.org