On Tuesday 15 January 2008, Donnie Berkholz wrote: > On 05:34 Tue 15 Jan , Rajiv Aaron Manglani (rajiv) wrote: > > 1.1 net-misc/zaptel/zaptel-1.2.22.1-r1.ebuild > > > > file : > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-misc/zaptel/zaptel-1. > >2.22.1-r1.ebuild?rev=1.1&view=markup plain: > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-misc/zaptel/zaptel-1. > >2.22.1-r1.ebuild?rev=1.1&content-type=text/plain > > > > # fix permissions if there's no udev around > > if [[ -d ${D}/dev/zap ]]; then > > chown -R root:dialout ${D}/dev/zap > > chmod -R u=rwX,g=rwX,o= ${D}/dev/zap > > fi > > You can check whether udev's around by looking for /dev/.udev -- that > way you don't hack around with /dev files for no reason.
but what about mdev ? devfs ? $random-magic-hotplug-flavor ?
> > # fix permissions if there's no udev around
> > if [[ -d ${ROOT}dev/zap ]]; then
> > chown -R root:dialout ${ROOT}dev/zap
> > chmod -R u=rwX,g=rwX,o= ${ROOT}dev/zap
> > fi
> > }
>
> And again..
i'd just straight up say that /dev/ management is the user's problem, not
ebuilds, and it's up to the user to dictate policies. keep the ebuilds
clean.
-mike
signature.asc
Description: This is a digitally signed message part.
