Re: Force Dependent ports OPTIONS

2014-05-10 Thread Chris Rees
Hi Muhammad,

On 04/05/2014 15:09, Muhammad Moinur Rahman wrote:
 Hi Dirk,
 
 How can I enforce it from inside a ports Makefile?
 
 Thanks in advance.
 

Short answer, you can't, sorry.

You'll need to test it somehow in a target;

pre-configure:
if ! openssl --help 21 | grep -q 3779; then \
${ECHO_MSG} openssl was compiled without RFC3779 option; ; \
${ECHO_MSG} please reinstall with RFC3779 selected; \
${FALSE}; \
fi

Not sure if anyone else has a better idea

By the way, check that openssl --help actually tells you whether or
not RFC3779 was compiled, because I don't know :)

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Force Dependent ports OPTIONS

2013-12-05 Thread Baptiste Daroussin
On Thu, Dec 05, 2013 at 05:42:15PM +0600, Muhammad Moinur Rahman wrote:
 Hi,
 
 Let us suppose I am porting an application which depends on Openssl. But
 not only OpenSSL, OpenSSL has to have some options enabled which are not
 enabled by default. How can I force changing the knob?
 
 Slave port is an option I have thought. But anything else? Thanks in
 advance.
 

Creating a slave port will be a nightmare for openssl, what option are you
depending on? is it intrusive, does it make sense to have it by default?

Those are the questions, depending on answers the good way could be to remove
the option from the openssl port and activate by default the feature.

regards,
Bapt


pgppwVgeSaAA_.pgp
Description: PGP signature


Re: Force Dependent ports OPTIONS

2013-12-05 Thread Muhammad Moinur Rahman
Hi Bapte,

RFC3779.

BR,
Muhammad


On Thu, Dec 5, 2013 at 5:45 PM, Baptiste Daroussin b...@freebsd.org wrote:

 On Thu, Dec 05, 2013 at 05:42:15PM +0600, Muhammad Moinur Rahman wrote:
  Hi,
 
  Let us suppose I am porting an application which depends on Openssl. But
  not only OpenSSL, OpenSSL has to have some options enabled which are not
  enabled by default. How can I force changing the knob?
 
  Slave port is an option I have thought. But anything else? Thanks in
  advance.
 

 Creating a slave port will be a nightmare for openssl, what option are you
 depending on? is it intrusive, does it make sense to have it by default?

 Those are the questions, depending on answers the good way could be to
 remove
 the option from the openssl port and activate by default the feature.

 regards,
 Bapt

___
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