On my machine, the modem is used as fax machine and as dialin server. It is a pain to change PATH_EGETTY to mgetty every time I upgrade hylafax My proposal is to define a new local use flag called mgetty. When this is set, PATH_EGETTY and PATH_VGETTY should be set to mgetty.
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.
