| Summary: | hylafax should have PATH_EGETTY/PATH_VGETTY configurable by use flags | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alin Năstac (RETIRED) <mrness> |
| Component: | Current packages | Assignee: | Mike Doty (RETIRED) <kingtaco> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nerdboy |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | usage of mgetty/vgetty for data/voice calls | ||
|
Description
Alin Năstac (RETIRED)
2005-04-14 00:20:38 UTC
You guys should set a bugzilla account for comm-fax can you be more specific or provide a patch for your proposal? Created attachment 57857 [details, diff]
usage of mgetty/vgetty for data/voice calls
this is what I had in mind
the patch looks fine, except for one thing; do we have to use hardcoded paths for mgetty? is there a better way of determining where mgetty is located? For example, what do we do if it's installed in /usr/local/sbin/ net-dialup/mgetty installs those executables in ${ROOT}/usr/sbin
I guess you could use 'which mgetty', but I don't see the reason - those paths are established by mgetty ebuild.
net-misc/hylafax-4.2.1-r1 incvs with the patch, additionally, I block having both "faxonly" and "mgetty" use flags set, as they affect the same configure parameters. |