Summary: | xprint require a profile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | INODE64 Sistemas <web> |
Component: | [OLD] Server | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | x11 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
sample profile
enviremont update ebuild to copy file to env.d |
Description
INODE64 Sistemas
2004-09-03 16:31:52 UTC
Created attachment 38858 [details, diff]
sample profile
Created attachment 41075 [details]
enviremont
this file copy in /etc/env.d
and run env-update
Created attachment 41076 [details, diff]
update ebuild to copy file to env.d
Attachment 41075 [details] assumes that if the xprint binary exist, the xprint init script does. Bad assumption. 38858 is better. It should be the init script's job to check for the binary, so you don't need to. You will want to check for a bad return from the init script though. I'm not sure whether there's any policy on quasi-dynamic env.d content.
The env.d stuff should just get appended to the end of 10xorg in the xorg-x11 ebuild rather than creating a new file since the independent xprint ebuild is apparently deprecated in favor of xorg's xprint.
this fix is deprecated in favor of xorg's xprint. |