Re: How to detect filename conflicts with uninstalled ports?
Charlie Kester wrote: I'm working on a new port that installs a program with a name that seems like it would already be taken, but I don't have anything by that name on my system -- even though I have lots of ports installed. I know that I can use portsdb -r to find all the ports that depend on a given port, whether they're installed or not. Is there a similar way to determine if an uninstalled port installs a file with a given name? You can use ports-mgmt/portsearch to search ports, contains some file. For example portsearch -f 'bin/bash$' -- LEFT-(UANIC|RIPE) JID: lev...@jabber.net.ua PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to detect filename conflicts with uninstalled ports?
Charlie Kester wrote: But I expect these two find greps will detect the majority of filename conflicts. Unless someone has a better recommendation, I'll settle for less than perfect. Using a MANIFEST file for packages works, if you have one available. It's simply a file listing of the contents of each and every package. Then just grep that ? --anders ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
How to detect filename conflicts with uninstalled ports?
I'm working on a new port that installs a program with a name that seems like it would already be taken, but I don't have anything by that name on my system -- even though I have lots of ports installed. I know that I can use portsdb -r to find all the ports that depend on a given port, whether they're installed or not. Is there a similar way to determine if an uninstalled port installs a file with a given name? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to detect filename conflicts with uninstalled ports?
On Sat 20 Nov 2010 at 17:23:37 PST Charlie Kester wrote:
I'm working on a new port that installs a program with a name that seems
like it would already be taken, but I don't have anything by that name
on my system -- even though I have lots of ports installed.
I know that I can use portsdb -r to find all the ports that depend on
a given port, whether they're installed or not. Is there a similar way
to determine if an uninstalled port installs a file with a given name?
As someone kindly reminded me, find and grep are my friends:
$ cd /usr/ports
$ find . -name pkg-plist -exec grep -H bin/progname {} \;
$ find . -name Makefile -exec grep -H bin/progname {} \;
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to detect filename conflicts with uninstalled ports?
Charlie Kester writes:
On Sat 20 Nov 2010 at 17:23:37 PST Charlie Kester wrote:
I'm working on a new port that installs a program with a name that seems
like it would already be taken, but I don't have anything by that name
on my system -- even though I have lots of ports installed.
I know that I can use portsdb -r to find all the ports that depend on
a given port, whether they're installed or not. Is there a similar way
to determine if an uninstalled port installs a file with a given name?
As someone kindly reminded me, find and grep are my friends:
$ cd /usr/ports
$ find . -name pkg-plist -exec grep -H bin/progname {} \;
$ find . -name Makefile -exec grep -H bin/progname {} \;
The former accounts for static packing lists; does the second
do the same for dynamic packing lists?
Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to detect filename conflicts with uninstalled ports?
On Sat 20 Nov 2010 at 19:33:01 PST Robert Huff wrote:
Charlie Kester writes:
On Sat 20 Nov 2010 at 17:23:37 PST Charlie Kester wrote:
I'm working on a new port that installs a program with a name that seems
like it would already be taken, but I don't have anything by that name
on my system -- even though I have lots of ports installed.
I know that I can use portsdb -r to find all the ports that depend on
a given port, whether they're installed or not. Is there a similar way
to determine if an uninstalled port installs a file with a given name?
As someone kindly reminded me, find and grep are my friends:
$ cd /usr/ports
$ find . -name pkg-plist -exec grep -H bin/progname {} \;
$ find . -name Makefile -exec grep -H bin/progname {} \;
The former accounts for static packing lists; does the second
do the same for dynamic packing lists?
Probably not. I was just thinking of ports that define PLIST_FILES in
their Makefiles, in lieu of a pkg-plist.
But I expect these two find greps will detect the majority of filename
conflicts. Unless someone has a better recommendation, I'll settle for
less than perfect.
Besides, the Porter's Handbook strongly discourages the use of dynamic
package lists (although it does not forbid them). So if I'm not aware
of a conflict with someone else's port that uses them anyway, I figure
it's as much their fault as mine. ;)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to detect filename conflicts with uninstalled ports?
Charlie Kester writes: But I expect these two find greps will detect the majority of filename conflicts. Unless someone has a better recommendation, I'll settle for less than perfect. If this is a one-time thing, your best policy might be to provide the (proposed) name and see if anyone raises a red flag. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to detect filename conflicts with uninstalled ports?
On Sat 20 Nov 2010 at 20:34:30 PST Robert Huff wrote: Charlie Kester writes: But I expect these two find greps will detect the majority of filename conflicts. Unless someone has a better recommendation, I'll settle for less than perfect. If this is a one-time thing, your best policy might be to provide the (proposed) name and see if anyone raises a red flag. Two names, actually: box and boxer. I'm amazed these names don't seem to be taken. I remember boxer as the name of an editor on another platform, but it was never ported to BSD. There's boxes which is a little utility for formatting comment blocks and similar text. But no box. Weird. Anyway, the box I have in mind is a programming language for graphics. http://boxc.sourceforge.net. Boxer is the name of its Python-based GUI. I have the portfiles ready to submit, assuming my tinderbox run goes OK. This query was one of my final sanity checks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
