These packages are almost always exclusive. Reproducible: Didn't try Steps to Reproduce: 1. Emerge hylafax ( version 4.1.8) 2. 3. Actual Results: emerged mgetty+sendfax then hylafax Expected Results: only emerge hylafax This surprised me greaty. hylafax and mgetty+sendfax are competitve packages, not compliementary packages.
This is true, and I'm not sure how to handle it because the mgetty ebuild includes everything. The rpm solution was to split the rpms into mgetty, mgetty-sendfax, etc; the hylafax spec file then specifies a conflict with mgetty-sendfax (but other mgetty rpms are ok). There appears to be a work-around for hylafax/mgetty/ppp, but it references an older version of redhat. That said, it looks like it might work, however, it requires manual setup by the user (it's fairly simple). Depending on the modem features, another solution using Adaptive Answer might work, which looks a bit more complicated than the above. It kinda depends on your perspective about what users would want to do with their [voice/]fax/modems, since there are several possible scenarios in terms of both incoming and outgoing voice/fax/data calls, as well as hardware. And Office vs. Home use can be quite different in terms of requirements. The only real conflicts I see are that hyalfax and mgetty both use the same spool dir (which is messy, but probably not fatal), and hylafax provides /usr/bin/sendfax, whereas mgetty provides /usr/sbin/sendfax (which has problems for root, calling sendfax without the full intended path, etc). I'm open to suggestions; should the default be to recommend unmerging mgetty first? Would slotting work, or maybe profiles? Obviously, I'm not a portage guru...
It does seems that mgetty+sendfax and hylafax are exclusive maybe creating a virtual/fax for both packages is the solution. The question remains. I didn't have mgetty+sendfax installed before I emerged hylafax. What is in there that hylafax needs? I think the answer is 'nothing' and the dependency is bogus. Regards, Dad
Have you unmerged mgetty and see if hylafax still works? I might not get to this for a day or two, so feel free to try a modified ebuild in your portage overlay if you want (ie, remove the mgetty dependency and emerge it).
what's the status of this, does hylafax work without mgetty?
I confess, I haven't tried it yet (but I'm making an ebuild now). I'm thinking mgetty should be split into two packages, ala DeadRat (ie, something like an mgetty-x and mgetty-sendfax-x) and then a virtual fax defined. The efax ebuild can also provide this capability (so a totlal of 3). I'm not sure about how to handle the mgetty/agetty/vgetty stuff (maybe the same way?). The previous post is probably correct about the bogus dependency; since I didn't create the original ebuild, I can't really speculate as to the rationale... So how do we get the above to happen?
The new hylafax 4.2.0_rc2 has a faxonly keyword to address the mgetty-sendfax issue. Set USE="faxonly" to remove the mgetty depend. Feel free to give it a whirl...
Try the faxonly flag on the 4.2.0 ebuild. Let me know how it owrks for you.
