Re: Vice versa of 'pkg_info -W'

2013-01-04 Thread Lars Engels
On Thu, Jan 03, 2013 at 06:47:53PM +0100, rank1see...@gmail.com wrote:
> > Am 02.01.2013 18:55, schrieb rank1see...@gmail.com:
> > > For example:
> > > # pkg_info -W /usr/local/bin/lynx
> > > /usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
> > >
> > > # pkg_deinstall lynx-2.8.7.2,1
> > >
> > > # pkg_info -W /usr/local/bin/lynx
> > > pkg_info: /usr/local/bin/lynx: file cannot be found
> > >
> > >
> > > As you can figure it out, I want a reverse method, that is ...
> > > If I want to have '/usr/local/bin/lynx' installed, which port
> > > origin(s), would install it?
> > >
> > 
> > 
> > I use porgle for that:
> > 
> > http://www.secnetix.de/tools/porgle/porgle.py
> >
> 
> Search in: => checked all boxes
> 
> 0 results for:"/usr/local/bin/lynx"
> 0 results for:"bin/lynx"
> 
> No matching ports found.
> 
> It doesn't work.
> 

It does. Just use the filename, not the path:

http://www.secnetix.de/tools/porgle/porgle.py?plst=1&q=tvbrowser&Search=Search



pgpB9UvGTktBZ.pgp
Description: PGP signature


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread Lev Serebryakov
Hello, Dieter.
You wrote 3 января 2013 г., 23:52:10:


DB> time find /usr/ports/ -name pkg-plist | xargs grep bin/lynx$

DB> Not bad for a system that has been repeatedly insulted on this
DB> list recently.
 The problem is, this is not a solution for OP's question, because
many ports have pkg-plist which is not full and is
created/updated/appended in build/install time :(

-- 
// Black Lion AKA Lev Serebryakov 

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread Dieter BSD
Domagoj writes:
> I've attempted to grep '/usr/ports/*/*/pkg-plist' for 'bin/lynx'
> and shot myself in a foot! :P
> Even if it did returned "sane" amount of matches, speed was atrocious.

time find /usr/ports/ -name pkg-plist | xargs grep bin/lynx$
/usr/ports/finance/ledgersmb/pkg-plist:@dirrm ledger-smb/bin/lynx
/usr/ports/finance/sql-ledger/pkg-plist:@dirrm sql-ledger/bin/lynx
/usr/ports/japanese/lynx/pkg-plist:bin/lynx
/usr/ports/japanese/lynx-current/pkg-plist:bin/lynx
/usr/ports/www/lynx/pkg-plist:bin/lynx
/usr/ports/www/lynx-current/pkg-plist:bin/lynx

real0m2.065s
user0m0.379s
sys 0m1.338s

Not bad for a system that has been repeatedly insulted on this
list recently.

(I'm assuming that 6 matches is a "sane" amount.)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread Daniel Eischen

On Thu, 3 Jan 2013, Freddie Cash wrote:


That tells you which installed port owns /usr/local/bin/foo.

It doesn't tell you which NOT-installed port would install
/usr/local/bin/foo, which is what the OP is wanting.


Ahh, Bach.

--
DE
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread rank1seeker
> >>> For example:
> >>> # pkg_info -W /usr/local/bin/lynx
> >>> /usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
> >>>
> >>> # pkg_deinstall lynx-2.8.7.2,1
> >>>
> >>> # pkg_info -W /usr/local/bin/lynx
> >>> pkg_info: /usr/local/bin/lynx: file cannot be found
> >>>
> >>>
> >>> As you can figure it out, I want a reverse method, that is ...
> >>> If I want to have '/usr/local/bin/lynx' installed, which port
> >>> origin(s), would install it?
> >>>
> >>
> >>
> >> I use porgle for that:
> >>
> >> 

http://www.secnetix.de/tools/**porgle/porgle.py
> >>
> >
> > For non-pkgng, what's wrong with pkgdb and pkg_which (portupgrade)?
> >
> >   # pkgdb -o `pkg_which /usr/local/bin/foo`
> >
> > And for pkgng:
> >
> >   # pkg which -o /usr/local/bin/foo
> >
> > Or am I missing something?
> >
> > --
> > DE
> > __**_
> > freebsd-hackers@freebsd.org mailing list
> > 

http://lists.freebsd.org/**mailman/listinfo/freebsd-**hackers
> > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@**
> > freebsd.org "
> >
> 
> 
> That tells you which installed port owns /usr/local/bin/foo.
> 
> It doesn't tell you which NOT-installed port would install
> /usr/local/bin/foo, which is what the OP is wanting.
> 
> 
> 
> -- 
> Freddie Cash
> fjwc...@gmail.com
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
> 


Exactly!
;)



Domagoj
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread rank1seeker
> Am 02.01.2013 18:55, schrieb rank1see...@gmail.com:
> > For example:
> > # pkg_info -W /usr/local/bin/lynx
> > /usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
> >
> > # pkg_deinstall lynx-2.8.7.2,1
> >
> > # pkg_info -W /usr/local/bin/lynx
> > pkg_info: /usr/local/bin/lynx: file cannot be found
> >
> >
> > As you can figure it out, I want a reverse method, that is ...
> > If I want to have '/usr/local/bin/lynx' installed, which port
> > origin(s), would install it?
> >
> 
> 
> I use porgle for that:
> 
> http://www.secnetix.de/tools/porgle/porgle.py
>

Search in: => checked all boxes

0 results for:"/usr/local/bin/lynx"
0 results for:"bin/lynx"

No matching ports found.

It doesn't work.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread Freddie Cash
That tells you which installed port owns /usr/local/bin/foo.

It doesn't tell you which NOT-installed port would install
/usr/local/bin/foo, which is what the OP is wanting.


On Thu, Jan 3, 2013 at 9:23 AM, Daniel Eischen  wrote:

> On Thu, 3 Jan 2013, Lars Engels wrote:
>
>  Am 02.01.2013 18:55, schrieb rank1see...@gmail.com:
>>
>>> For example:
>>> # pkg_info -W /usr/local/bin/lynx
>>> /usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
>>>
>>> # pkg_deinstall lynx-2.8.7.2,1
>>>
>>> # pkg_info -W /usr/local/bin/lynx
>>> pkg_info: /usr/local/bin/lynx: file cannot be found
>>>
>>>
>>> As you can figure it out, I want a reverse method, that is ...
>>> If I want to have '/usr/local/bin/lynx' installed, which port
>>> origin(s), would install it?
>>>
>>
>>
>> I use porgle for that:
>>
>> http://www.secnetix.de/tools/**porgle/porgle.py
>>
>
> For non-pkgng, what's wrong with pkgdb and pkg_which (portupgrade)?
>
>   # pkgdb -o `pkg_which /usr/local/bin/foo`
>
> And for pkgng:
>
>   # pkg which -o /usr/local/bin/foo
>
> Or am I missing something?
>
> --
> DE
> __**_
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@**
> freebsd.org "
>



-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread Daniel Eischen

On Thu, 3 Jan 2013, Lars Engels wrote:


Am 02.01.2013 18:55, schrieb rank1see...@gmail.com:

For example:
# pkg_info -W /usr/local/bin/lynx
/usr/local/bin/lynx was installed by package lynx-2.8.7.2,1

# pkg_deinstall lynx-2.8.7.2,1

# pkg_info -W /usr/local/bin/lynx
pkg_info: /usr/local/bin/lynx: file cannot be found


As you can figure it out, I want a reverse method, that is ...
If I want to have '/usr/local/bin/lynx' installed, which port
origin(s), would install it?



I use porgle for that:

http://www.secnetix.de/tools/porgle/porgle.py


For non-pkgng, what's wrong with pkgdb and pkg_which (portupgrade)?

  # pkgdb -o `pkg_which /usr/local/bin/foo`

And for pkgng:

  # pkg which -o /usr/local/bin/foo

Or am I missing something?

--
DE
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread Lars Engels

Am 02.01.2013 18:55, schrieb rank1see...@gmail.com:

For example:
# pkg_info -W /usr/local/bin/lynx
/usr/local/bin/lynx was installed by package lynx-2.8.7.2,1

# pkg_deinstall lynx-2.8.7.2,1

# pkg_info -W /usr/local/bin/lynx
pkg_info: /usr/local/bin/lynx: file cannot be found


As you can figure it out, I want a reverse method, that is ...
If I want to have '/usr/local/bin/lynx' installed, which port
origin(s), would install it?




I use porgle for that:

http://www.secnetix.de/tools/porgle/porgle.py


___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-03 Thread rank1seeker
> rank1see...@gmail.com wrote:
> 
> >For example:
> ># pkg_info -W /usr/local/bin/lynx
> >/usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
> >
> ># pkg_deinstall lynx-2.8.7.2,1
> >
> ># pkg_info -W /usr/local/bin/lynx
> >pkg_info: /usr/local/bin/lynx: file cannot be found
> >
> >
> >As you can figure it out, I want a reverse method, that is ...
> >If I want to have '/usr/local/bin/lynx' installed, which port
> >origin(s), would install it?
> 
> The portsearch port will do that.
> 

Well, it works prety much as:


> Well, in the case of lynx, where the filename of the executable matches
> the package name, it's fairly simple:
> 
> lucid-nonsense:/usr/ports:% cd /usr/ports
> lucid-nonsense:/usr/ports:% make search name=lynx
> Port: ja-lynx-2.8.7.r1
> Path: /usr/ports/japanese/lynx
> Info: A terminal-based World-Wide Web Client with multi-byte modification
> Maint:po...@freebsd.org
> B-deps:   libiconv-1.14
> R-deps:   libiconv-1.14
> WWW:  http://lynx.isc.org/current/
> 
> Port: ja-lynx-2.8.8.d3
> Path: /usr/ports/japanese/lynx-current
> Info: A terminal-based World-Wide Web Client with multi-byte
> modification (development version)
> Maint:po...@freebsd.org
> B-deps:   libiconv-1.14
> R-deps:   libiconv-1.14
> WWW:  http://lynx.isc.org/current/
> 
> Port: lynx-2.8.7.2,1
> Path: /usr/ports/www/lynx
> Info: A non-graphical, text-based World-Wide Web client
> Maint:jhar...@widomaker.com
> B-deps:   gettext-0.18.1.1 libiconv-1.14 openssl-1.0.1_4
> R-deps:   gettext-0.18.1.1 libiconv-1.14 openssl-1.0.1_4
> WWW:  http://lynx.isc.org/
> 
> Port: lynx-2.8.8d12_1
> Path: /usr/ports/www/lynx-current
> Info: A non-graphical, text-based World-Wide Web client
> Maint:joh...@freebsd.org
> B-deps:   gettext-0.18.1.1 libiconv-1.14 libidn-1.25 openssl-1.0.1_4
> pkgconf-0.8.9
> R-deps:   gettext-0.18.1.1 libiconv-1.14 libidn-1.25 mime-support-3.52.2
> openssl-1.0.1_4 pkgconf-0.8.9
> WWW:  http://lynx.isc.org/current/
> 

I slightly hopped '-p path' flag of a portsearch would to the trick, but it 
counts for '/usr/ports/*' path.
Not to the path of a binary.

> 
> However, in the general case, there isn't (as far as I know) a database
> of all of the files installed by all of the packages that can be
> generated from the ports.

Unfortunately.
I've attempted to grep '/usr/ports/*/*/pkg-plist' for 'bin/lynx' and shot 
myself in a foot! :P
Even if it did returned "sane" amount of matches, speed was atrocious.

> I believe bapt@ had plans to gather this sort of data on the
> yet-to-be-commisioned pkgng build cluster.  As that's currently out of
> action as a consequence of the security incident, and the whole package
> building system is being revised, I don't know if that's still on the
> cards or likely to be implemented any time soon.
> 
>   Cheers,
> 
>   Matthew

I see. But for this to work, DB is mandatory.


Domagoj Smolčić
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: Vice versa of 'pkg_info -W'

2013-01-02 Thread Mike Meyer
rank1see...@gmail.com wrote:

>For example:
># pkg_info -W /usr/local/bin/lynx
>/usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
>
># pkg_deinstall lynx-2.8.7.2,1
>
># pkg_info -W /usr/local/bin/lynx
>pkg_info: /usr/local/bin/lynx: file cannot be found
>
>
>As you can figure it out, I want a reverse method, that is ...
>If I want to have '/usr/local/bin/lynx' installed, which port
>origin(s), would install it?

The portsearch port will do that.

-- 
Sent from my Android phone. Please excuse my swyping.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"


Re: Vice versa of 'pkg_info -W'

2013-01-02 Thread Matthew Seaman
On 02/01/2013 17:55, rank1see...@gmail.com wrote:
> For example:
> # pkg_info -W /usr/local/bin/lynx
> /usr/local/bin/lynx was installed by package lynx-2.8.7.2,1
> 
> # pkg_deinstall lynx-2.8.7.2,1
> 
> # pkg_info -W /usr/local/bin/lynx
> pkg_info: /usr/local/bin/lynx: file cannot be found
> 
> 
> As you can figure it out, I want a reverse method, that is ...
> If I want to have '/usr/local/bin/lynx' installed, which port origin(s), 
> would install it?

Well, in the case of lynx, where the filename of the executable matches
the package name, it's fairly simple:

lucid-nonsense:/usr/ports:% cd /usr/ports
lucid-nonsense:/usr/ports:% make search name=lynx
Port:   ja-lynx-2.8.7.r1
Path:   /usr/ports/japanese/lynx
Info:   A terminal-based World-Wide Web Client with multi-byte modification
Maint:  po...@freebsd.org
B-deps: libiconv-1.14
R-deps: libiconv-1.14
WWW:http://lynx.isc.org/current/

Port:   ja-lynx-2.8.8.d3
Path:   /usr/ports/japanese/lynx-current
Info:   A terminal-based World-Wide Web Client with multi-byte
modification (development version)
Maint:  po...@freebsd.org
B-deps: libiconv-1.14
R-deps: libiconv-1.14
WWW:http://lynx.isc.org/current/

Port:   lynx-2.8.7.2,1
Path:   /usr/ports/www/lynx
Info:   A non-graphical, text-based World-Wide Web client
Maint:  jhar...@widomaker.com
B-deps: gettext-0.18.1.1 libiconv-1.14 openssl-1.0.1_4
R-deps: gettext-0.18.1.1 libiconv-1.14 openssl-1.0.1_4
WWW:http://lynx.isc.org/

Port:   lynx-2.8.8d12_1
Path:   /usr/ports/www/lynx-current
Info:   A non-graphical, text-based World-Wide Web client
Maint:  joh...@freebsd.org
B-deps: gettext-0.18.1.1 libiconv-1.14 libidn-1.25 openssl-1.0.1_4
pkgconf-0.8.9
R-deps: gettext-0.18.1.1 libiconv-1.14 libidn-1.25 mime-support-3.52.2
openssl-1.0.1_4 pkgconf-0.8.9
WWW:http://lynx.isc.org/current/


However, in the general case, there isn't (as far as I know) a database
of all of the files installed by all of the packages that can be
generated from the ports.

I believe bapt@ had plans to gather this sort of data on the
yet-to-be-commisioned pkgng build cluster.  As that's currently out of
action as a consequence of the security incident, and the whole package
building system is being revised, I don't know if that's still on the
cards or likely to be implemented any time soon.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.

PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk



signature.asc
Description: OpenPGP digital signature