On Sat, 16 Apr 2011 18:26:38 -0500, Dale wrote:
> Some put them in the overlay to test then move them over to the tree a
> bit later if there are no problems or weird dependency problems.
>
> I think there is a fancy command to get that info but can't recall it
> at the moment. I bet someone wi
On Sun, Apr 17, 2011 at 1:52 AM, Michael George wrote:
> I just got a new scanner which will be supported in version 1.0.22 of
> the sane-backend package. However, that version isn't in portage yet.
> How do I find who the maintainers of the portage package are so that I
> can contact them to see
Dale wrote:
Michael George wrote:
I just got a new scanner which will be supported in version 1.0.22 of
the sane-backend package. However, that version isn't in portage yet.
How do I find who the maintainers of the portage package are so that I
can contact them to see if I can help get that por
Michael George wrote:
I just got a new scanner which will be supported in version 1.0.22 of
the sane-backend package. However, that version isn't in portage yet.
How do I find who the maintainers of the portage package are so that I
can contact them to see if I can help get that port made availa
I just got a new scanner which will be supported in version 1.0.22 of
the sane-backend package. However, that version isn't in portage yet.
How do I find who the maintainers of the portage package are so that I
can contact them to see if I can help get that port made available?
--
-M
There are
Well, here we are again. Sane-backends gives me this error:
> make[1]: Leaving directory
> `/var/tmp/portage/sane-backends-1.0.18-r2/work/sane-backends-1.0.18/sanei'
> making all in backend
> make[1]: Entering directory
> `/var/tmp/portage/sane-backends-1.0.18-r2/work/sane-backends-1.0.18/backend
6 matches
Mail list logo
