Re: Best way to exterminate a port

On 12/07/2016 01:27, bob prohaska wrote: > Is there an easy way to "rip out by the roots" a botched > port install and start over, including re-doing all the > configuration dialogs of the port and its dependencies? > > Thanks for reading, # cd /usr/ports/some/thing # make rmconfig-recursive # ma

Re: Best way to exterminate a port

On Mon, Jul 11, 2016 at 10:33 PM, Freddie Cash wrote: > On Jul 11, 2016 10:22 PM, "Kurt Jaeger" wrote: > > > > Hi! > > > > > Is there an easy way to "rip out by the roots" a botched > > > port install and start over, including re-doing all the > > > configuration dialogs of the port and its depe

Re: Best way to exterminate a port

On Jul 11, 2016 10:49 PM, "Kurt Jaeger" wrote: > > Hi! > > > > > Is there an easy way to "rip out by the roots" a botched > > > > port install and start over, including re-doing all the > > > > configuration dialogs of the port and its dependencies? > > > > > > For one port: > > > > > > pkg delete

Re: Best way to exterminate a port

Hi! > > > Is there an easy way to "rip out by the roots" a botched > > > port install and start over, including re-doing all the > > > configuration dialogs of the port and its dependencies? > > > > For one port: > > > > pkg delete port > > > > cd /usr/ports/<...> > > > > make rmconfig > > Isn't

Re: base components should always be default (Re: change in default openssl coming)

Kevin Oberman wrote: On Mon, Jul 11, 2016 at 1:10 PM, Michelle Sullivan > wrote: Wojciech Puchar wrote: Interesting question. Perl was removed from the base system years ago with no ill affects. ssh ...?

Re: Best way to exterminate a port

On 12.07.2016 07:33, Freddie Cash wrote: On Jul 11, 2016 10:22 PM, "Kurt Jaeger" wrote: Hi! Is there an easy way to "rip out by the roots" a botched port install and start over, including re-doing all the configuration dialogs of the port and its dependencies? For one port: pkg delete p

Re: base components should always be default (Re: change in default openssl coming)

On 09.07.2016 18:25, Kevin Oberman wrote: > This discussion has now been going on for a while. Several times the > question "Why should be do this?" has been asked and answered, but I want > to know why it is desirable to have ports use the base OpenSSL. I thought, I explained my thinking for this

Re: security/w3af update

Hi! > I wrote an update for security/w3af and the hole was deeper than I thought. Thanks! That looks very interesting! > It was necessary several new ports as dependency: [...] > I did not open a PR yet... I am wondering if is better open a new PR for > each dependency or just one PR for securit

pkg-fallout complaining about libexecinfo

Hello, I've received messages with port build failure http://beefy2.nyi.freebsd.org/data/93amd64-default/418411/logs/zoneminder-1.30.0_1.log cd /wrkdirs/usr/ports/multimedia/zoneminder/work/ZoneMinder-1.30.0-rc1/src && /usr/local/bin/cmake -E cmake_link_script CMakeFiles/zma.dir/link.txt --v

FreeBSD Port: audio/HVSC-Update

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

Re: Deluge 1.3.x and libtorrent-rasterbar v1.1.0

On 11.07.2016 09:46, Bendik wrote: > Latest version of libtorrent-rasterbar is now 1.1.0, and ports has v1.0.9 > so it might be tempting to update it (like Arch did without testing). Khm, I have the update (almost) ready here -- and testing it with net-p2p/qbittorrent... > However, libtorrent v1.1.

devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency

I'm the maintainer of devel/sope2 (required for www/sogo2). Upon updating the port for an upstream version increment, I now get an error running "make" when DEVELOPER=yes is set in /etc/make.conf. The upstream project is in maintainence so I'm almost certain there's no changes in the upstream s

Re: Deluge 1.3.x and libtorrent-rasterbar v1.1.0

Patching Deluge 1.3.x is not straight forward, so I wouldn't go that route just yet. It looks like the fix to the CVE will be backported to libtorrent v1.0: https://github.com/arvidn/libtorrent/issues/780 Regards Bendik On Tue, Jul 12, 2016 at 3:23 PM, Mikhail T. wrote: > On 11.07.2016 09:46,

pulseview 0.4.0 not linking. Help with Qt5 app build?

I'm working on new versions of the sigrok ports (libserialport, libsigrok, libsigrokdecode and pulseview being the critical bits). While the C things all build and seem to work with little problem, the GUI package - pulseview - fails to link with a bunch of references to undefined variables. Those

freebsd panics with wct4xxp driver

Hi, We are working to setup an asterisk-based PBX in the office. Everything worked until we decided to deploy ISDN PRI E1 links with the following hw/sw configuration: Hardware: - Intel Core i5 + 4G RAM - Digium Wildcard TE405P (2nd Gen) (4 TE span PCI-e PRI card) Software: - FreeBSD 9

Re: security/w3af update

On Tue, Jul 12, 2016 at 7:43 AM, Kurt Jaeger wrote: > Hi! > > > I wrote an update for security/w3af and the hole was deeper than I > thought. > > Thanks! That looks very interesting! > > > It was necessary several new ports as dependency: > [...] > > I did not open a PR yet... I am wondering if i

www/cakephp update request

Hello, I am setting up a port that depends on CakePHP. This seems to be outdated in current www/cakephp23. 3 is out already. Would that be possible to update the port please? :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-ports@

Framework question....

Ports Folks, I have a port (mail/dovecot2-pigeonhole) that I apparently need to pick up the mail/dovecot2 gssapi option, but do NOT want to make the user set it via the normal options dialog. I.E. if dovecot2 has gssapi_heimdal set, I want to know that. Does the framework give me a way to