From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: layman printer trouble
Date: Tue, 09 Oct 2012 12:08:37 +0200 [thread overview]
Message-ID: <5073F7A5.1010706@fu-berlin.de> (raw)
In-Reply-To: <loom.20121008T021926-626@post.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08.10.2012 14:52, James wrote:
> Hinnerk van Bruinehsen <h.v.bruinehsen <at> fu-berlin.de> writes:
>
>
>> Ok - you're trying two different approaches at the same time.
>> I'd recommend you to just use the printer-drivers overlay.
>
> Yep know doubts, I looked at too many different wiki and other
> googled resources. I could not find a simple here are the steps to
> installing "printer" overlays, compiling them, making the config
> changes and then testing via CUPS.
>
> OK, I'll the print drivers first.
>
>> Normally layman should take care of the contents of
>> /var/lib/layman/make.conf. Maybe it doesn#t work because you
>> created an empty one. You could try to simply delete it and
>> afterwards rerun layman -a printer-drivers. If that doesn't solve
>> your problem, recreate the file with the following content:
>
>> PORTDIR_OVERLAY=" $PORTDIR_OVERLAY"
>
>> Afterwards try layman -a printer-drivers again.
>
> #layman -l * printer-drivers [Git ]
> (git://git.o.g.o/proj/printer-drivers.git ) * zugaina
> [Rsync ] (rsync://gentoo.zugaina.org/zugaina-portage )
>
> OK it's installed. I would think emerging it is next? But that does
> not seem to work with emerge?
Sounds fine up to here. Make sure you have a line "source
/var/lib/layman/make.conf" inside your make.conf and try to emerge the
driver. It should work then.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQc/elAAoJEJwwOFaNFkYccQgH/j5PPQOOLoz04NmohiiqpSCQ
6xZ6X3qq1KgzUlJOXnQ2YnQpbaVGB1vTGddXCxytPfqSucCVFWCZkP/HsqrShWss
f7u2SaXmTP4TDoqx0tFpyReRhhv7hZATcGH9PpWVc+G8iSnyB5HJZOVzWFhPow/9
xXE3YxdKvEYPnru+LwjOBBVQJ1ktRsHbi2j6nQm5LTcZtSOrUq+OeEpRru5uswv5
ALruHbz8o90DeQycMyjXaDnwMcQ2o9IIdarVWSTaaxhCONB4OXC4XJ7egOJdC+Qa
DUB0myfNwKInn7hoqVV2cZys4tOIJ/+imiz0BYEKJR72roKm7B/chKFunWlooSE=
=e0Eu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-09 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 15:38 [gentoo-user] layman printer trouble Jamse
2012-10-05 18:57 ` Hinnerk van Bruinehsen
2012-10-05 19:39 ` [gentoo-user] " James
2012-10-05 21:21 ` Hinnerk van Bruinehsen
2012-10-08 12:52 ` James
2012-10-09 10:08 ` Hinnerk van Bruinehsen [this message]
2012-10-09 18:19 ` James
2012-10-09 18:30 ` James
2012-10-09 18:41 ` Hinnerk van Bruinehsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5073F7A5.1010706@fu-berlin.de \
--to=h.v.bruinehsen@fu-berlin.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox