Source Mage code commit list

[Eric Sandall <eric AT sandall.us>]

-----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:
>>>>> Excessive quoting removed
>>> I'm not sure what a sane default for udev would contain. Certainly the
>>> rules to move device nodes to subdirectories (e.g. alsa nodes in
>>> /dev/snd) as those are required by applications/libraries using that
>>> stuff.
>>> If we want to go the bare bones config + optional candy way, the basic
>>> rules should only contain the above and whatever is necessary
>>> permission/group wise to get sorcery working.
>>> With our current rules, there is indeed quite a bit of policy involved,
>>> including group settings and permissions for devices, but for most users
>>> this makes stuff a lot easier (i.e. they just have to add their users to
>>> the audio group to get sound). Udev makes it reasonably easy (albeit not
>>> trivial) to change all of those settings without touching our
>>> spell-installed rules files, so I think we can continue with our current
>>> ruleset, though it probably wouldn't hurt to modularize it a bit more.
>> 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).

- -sandalle

- --
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEY127HXt9dKjv3WERAj1oAKCrzpxBUY5D/XBjeoMsfjLJz4ReDwCgoSib
wgU05mZ2JBhqpDqnu9fevHw=
=WNvU
-----END PGP SIGNATURE-----