I'm interested in using HylaFAX for faxing, and mgetty (on a completely separate modem) for dialout support. However, building mgetty installs a number of files which conflict with HylaFAX. Having a USE flag for mgetty which avoids installing fax-specific components would be a Good Thing. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of bug 175973 ***
I do not agree that this is a duplicate of #175973. This bug asks to be able to install mgetty without sendfax; the other asks to be able to install hylafax without mgetty when no USE flags are set.
yeah, (In reply to comment #2) > I do not agree that this is a duplicate of #175973. This bug asks to be able to > install mgetty without sendfax; the other asks to be able to install hylafax > without mgetty when no USE flags are set. Then set USE=faxonly.
I do have USE=faxonly set; that does not address my issue, which is with the mgetty package (not with hylafax). I'm interested in using mgetty for modem (not fax-based) dialin on a completely separate modem (on the same machine as HylaFAX, but not interoperating in any other way). Because it always installs its own sendfax binary and puts its own content in /var/spool/fax, mgetty does not play along well with hylafax. If fax support for mgetty were a USE flag for the mgetty package, it would be possible to build mgetty for its non-faxing-related functionality while still using HylaFAX on the same machine; *that* is my goal.