On Wednesday, 15 August 2018 12:45:05 BST Franz Fellner wrote:
> I think that's the way "equery w" works:
> >> Display the path to the ebuild that would be used by Portage with the
>
> current configuration. <<
> With your current configuration there is no package matching your query.
>
>
I think that's the way "equery w" works:
>> Display the path to the ebuild that would be used by Portage with the
current configuration. <<
With your current configuration there is no package matching your query.
Alternatives for future use in such cases:
❯ epkginfo -k kyocera-1x2x-mfp-driver
*
On 15 August 2018 at 11:22, Peter Humphrey wrote:
> On Wednesday, 15 August 2018 09:50:09 BST Franz Fellner wrote:
> (atom) peak / # equery w net-print/kyocera-1x2x-mfp-driver
>
> Something does seem to be, if not broken, somewhat bent.
That seems to be correct. equery w takes your configuration
On Wednesday, 15 August 2018 09:50:09 BST Franz Fellner wrote:
>
> Am Mi., 15. Aug. 2018 um 11:29 Uhr schrieb Peter Humphrey <
>
> pe...@prh.myzen.co.uk>:
> > Hello list,
> >
> > While trying to get a USB printer recognised on an Atom box, I found
> > this, immediately after emerge --sync &&
It's ~amd64 only. So if you get missing keyword, could it be you are on x86?
Am Mi., 15. Aug. 2018 um 11:29 Uhr schrieb Peter Humphrey <
pe...@prh.myzen.co.uk>:
> Hello list,
>
> While trying to get a USB printer recognised on an Atom box, I found this,
> immediately after emerge --sync &&
Hello list,
While trying to get a USB printer recognised on an Atom box, I found this,
immediately after emerge --sync && eix-update:
(atom) peak / # eix -c kyocera
[N] net-print/kyocera-1x2x-mfp-driver (--): Printer descriptions (PPDs) and
filters for Kyocera 1x2x MFP
[N]
6 matches
Mail list logo