Re: port net/openldap24-sasl-client fails to register as dependency

Hello, (I am adding freebsd-ports@ to the thread as you suggested) Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Panagiotis, Panagiotis Christias wrote: Hello, I came across another dependency bug. It looks like packages that depend on net/openldap24-client (e.g. mail

Re: port net/openldap24-sasl-client fails to register as dependency

Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Panagiotis Christias wrote: Hello, (I am adding freebsd-ports@ to the thread as you suggested) Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Panagiotis, Panagiotis Christias wrote: Hello, I came across

Re: port net/openldap24-sasl-client fails to register as dependency

Boris Samorodov wrote: On Fri, 22 May 2009 06:08:58 +0300 Panagiotis Christias wrote: Ok, then how about dropping the net/openldap24-sasl-client port and adding an SASL OPTIONS entry to the net/openldap24-client port, like the server port? Then those who use packages will loose a possibility

Re: port net/openldap24-sasl-client fails to register as dependency

Uwe Laverenz wrote: Panagiotis Christias schrieb: I am already using that. Without it portinstall/upgrade would try every time to install net/openldap24-client (and fail). But it still does not register the dependency. There is a "knob" for this problem that should help you,

Re: pkg_add -r could be better?

On Fri, Oct 29, 2010 at 1:57 AM, Aragon Gouveia wrote: > Hi, > > On 10/28/10 22:07, Sean McAfee wrote: >> >> Why are you using -r (which fetches the default packages from >> freebsd.org/mirrors) in conjunction with custom packages? > > My intention is to serve them to multiple systems from a singl

Re: php53-pdo_mysql fail with MYSQLND

On 3/8/2012 23:44, Michael Ranner wrote: Hello! I have trouble with upgrading php53-pdo_mysql (5.3.14 to 5.3.15) on several systems, where I try to upgrade with portmaser. Build works without option MYSQLND but breaks with MYSQLND. Probably this have something to do with ports/169959. poudrier

WITHOUT_NLS precedence over {UNIQUENAME}_SET or OPTIONS_FILE_SET?

Hello, in my servers I add all global and per port build options in the /etc/make.conf file, like this: # Global options WITHOUT_NLS=yes [etc..] # Per port options .if $(.CURDIR:M*/mail/mailman) mailman_SET+=MTA SENDMAIL NLS .endif .if $(.CURDIR:M*/sysutils/coreutils) coreutil

Re: WITHOUT_NLS precedence over {UNIQUENAME}_SET or OPTIONS_FILE_SET?

On 25/7/2013 4:33 μμ, Tijl Coosemans wrote: On Thu, 25 Jul 2013 00:58:12 +0300 Panagiotis Christias wrote: in my servers I add all global and per port build options in the /etc/make.conf file, like this: # Global options WITHOUT_NLS=yes [etc..] # Per port options .if

How to "portinstall -P" packages that alter ther names via PKGNAMESUFFIX?

Hello, we were looking for a way to manage efficiently the ports installed in our servers and we came up with the idea to set up a "builder" server on which we compile, install and test all ports. The rest of our servers set the PKG_SITES variable to "builder" and use "portinstall -P" and "por

Re: How to "portinstall -P" packages that alter ther names via PKGNAMESUFFIX?

RW wrote: On Wed, 15 Apr 2009 02:24:59 +0300 Panagiotis Christias wrote: The setup works quite well and has saved us a lot of time and effort. Currently we are looking for ways to automate as much as possible the whole process. One of the problems we face is the initial installation of