Vice versa of 'pkg_info -W'

[rank1seeker at 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<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 at freebsd.org mailing list
> > 

http://lists.freebsd.org/**mailman/listinfo/freebsd-**hackers<http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>
> > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@**
> > freebsd.org <freebsd-hackers-unsubscribe at 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
> fjwcash at gmail.com
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
> 


Exactly!
;)



Domagoj