Hi, I used the debian patch, because there package is maintained and tested and has all the patches applied, which are needed to make it work again.
Created attachment 44498 [details] capi4hylafax-01.02.03.ebuild
Compiles for me on both x86 and amd64, allthough I cannot test it. Could someone test this for me?
Oh I gorget to say that I did not test this either, because my hylafax system is not yet working. But it needs testing as debian has maybe changed some important paths.
I added the following to avoid all path issues: mv ${S}.orig ${S} cd ${S} epatch ${WORKDIR}/capi4hylafax_${PV}-7.diff + for i in * debian/* src/scripts/setupconffile + do + if [ -f "${i}" ]; then + sed -si "s:/var/spool/hylafax:/var/spool/fax:" ${i} + fi + done }
Created attachment 44843 [details] capi4hylafax-01.02.03.ebuild This version seems to work(just my patch merged in), at least I get in gfax: HylaFAX scheduler on butler.genstef.homelinux.org: Running Modem faxCAPI (+49.89.67989331): Running and idle
oh, damn, I also made an ebuild for this. I check this one attached here and if mine has some further/other enhancements, I try to merge them and attach the new ebuild. Gimme a few mins... ;-)
ok, almost finished. But I'm not sure, if I should change the default "uucp" user to "fax" in all the config-files. SuSE enforces in their spec-files the user "fax" and group "uucp". The current ebuild also mention the user "fax". But all config-files are still using "uucp". hmm...
Ok, debian-changelog says this: * Switched back FaxReceiveUser to uucp since hylafax-server runs also as uucp and they're right.
ok, last checks are running. Then I attach my ebuild.
Created attachment 45093 [details] capi4hylafax-01.02.03.ebuild (enhanced) the promised enhanced version. Please test it!
What do you think of DEPEND RDEPEND? I think we should only have RDEPEND="net-dialup/capi4k-utils net-misc/hylafax" there. DEPEND defaults to RDEPEND if empty.
I agree with you. But I've taken this from your ebuild. So it's up to you. reduce it to a bare minimum. btw: I'm writing a new/better init-script. The old one is, well ..., not really good. The new one will be fully compatible, so you can just overwrite it in the $FILESDIR.
btw: RDEPEND equals to DEPEND if empty. So you should define only DEPEND.
Created attachment 45164 [details] capi4hylafax new and better init-script. put it into $FILESDIR. supports more than one config-file by just symlinking it to capi4hylafax.<device>, where <device> is the name of the config-file suffix (=modem). it's fully compatible to the old one.
Created attachment 45165 [details] capi4hylafax (init-script) fixed typo.
@ Mike: it works. If it compiles for you, then it works (if CAPI works of course).
nerdboy allowed me to take this one :) Where do you know the DEPEND/RDEPEND thing from? I want to set up a bookmark to prevent further mistakes.
[/usr/portage/skel.ebuild] # Build-time dependencies, such as # ssl? ( >=dev-libs/openssl-0.9.6b ) # >=dev-lang/perl-5.6.1-r1 # It is advisable to use the >= syntax show above, to reflect what you # had installed on your system when you tested the package. Then # other users hopefully won't be caught without the right version of # a dependency. DEPEND="" # Run-time dependencies, same as DEPEND if RDEPEND isn't defined: #RDEPEND=""
in portage, with DEPEND="net-dialup/capi4k-utils net-misc/hylafax" and all your changes :)
thanks. :)
