| 1 |
On Tuesday 15 January 2008, Donnie Berkholz wrote: |
| 2 |
> On 05:34 Tue 15 Jan , Rajiv Aaron Manglani (rajiv) wrote: |
| 3 |
> > 1.1 net-misc/zaptel/zaptel-1.2.22.1-r1.ebuild |
| 4 |
> > |
| 5 |
> > file : |
| 6 |
> > http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-misc/zaptel/zaptel-1. |
| 7 |
> >2.22.1-r1.ebuild?rev=1.1&view=markup plain: |
| 8 |
> > http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-misc/zaptel/zaptel-1. |
| 9 |
> >2.22.1-r1.ebuild?rev=1.1&content-type=text/plain |
| 10 |
> > |
| 11 |
> > # fix permissions if there's no udev around |
| 12 |
> > if [[ -d ${D}/dev/zap ]]; then |
| 13 |
> > chown -R root:dialout ${D}/dev/zap |
| 14 |
> > chmod -R u=rwX,g=rwX,o= ${D}/dev/zap |
| 15 |
> > fi |
| 16 |
> |
| 17 |
> You can check whether udev's around by looking for /dev/.udev -- that |
| 18 |
> way you don't hack around with /dev files for no reason. |
| 19 |
|
| 20 |
but what about mdev ? devfs ? $random-magic-hotplug-flavor ? |
| 21 |
|
| 22 |
> > # fix permissions if there's no udev around |
| 23 |
> > if [[ -d ${ROOT}dev/zap ]]; then |
| 24 |
> > chown -R root:dialout ${ROOT}dev/zap |
| 25 |
> > chmod -R u=rwX,g=rwX,o= ${ROOT}dev/zap |
| 26 |
> > fi |
| 27 |
> > } |
| 28 |
> |
| 29 |
> And again.. |
| 30 |
|
| 31 |
i'd just straight up say that /dev/ management is the user's problem, not |
| 32 |
ebuilds, and it's up to the user to dictate policies. keep the ebuilds |
| 33 |
clean. |
| 34 |
-mike |
Archives