Hi, i have some problems which i'll be able to solve but which are I think
annoying for new users.
- apsfilter installs its basedir in /usr/etc/apsfilter not in /etc. KDE lprng
wizard expects it in /etc which results in errors when trying to use the KDE
LPRNG wizard with Gentoo's LPRNG installation.
- Gentoo's apsfilter ebuild puts a printcap in /etc/lprng/ when using lprng,
/etc/cups/ when using cups, /etc/lpr/ when using lpr. KDE's wizard expects
printcap to be just in /etc/.
- USE "lprng" is NOT listed in use.desc, so installing lprng and apsfilter
without 'USE'ing "lprng" will result in apsfilter putting printcap in
/etc/printcap and lprng trying to read /etc/lprng/printcap.
So I would suggest always put any /etc/printcap just in /etc. It's such an
often used place. Of course I can symlink (and this is how I will solve it,
but it's not elegant)
nothing should be installed into /usr/etc
packages that do should be reported as bugs
apsfilter _does_ install at /usr/etc so I announce this as bug :)
on the other hand, it seems to work, but I still can't print, though. lprng's
checkpc, lp* are satisfied, at least. But the apsfilter is working until the end
drop a line, if you are interested in debugging apsfilter and lprng for my case.
please give to 'the printing dude'
me, happily, again.
There is not really a problem with apsfilter having at /usr/etc.
Apsfilter uses /etc/printcap, indeed, for configuration, while lprng expects
printcap at /etc/lprng/.
-> I had to cp /etc/printcap to /etc/lprng/. to get printing work.
Why the hell do I have to use /dev/lp1 aka /dev/printers/1 if I only have one
parallel printer device???
Does it depend on the parallel zip drive, I use?
fixed bugs in the ebuild & adding symlink now ..
does that work now?
noone reopened it so i close the bug