Re: Configuring options/knobs without `make config`

2017-07-31 Thread Jonathan Chen
On 1 August 2017 at 08:16, Morse, Richard E.,MGH
 wrote:
> On Jul 31, 2017, at 4:06 PM, Jonathan Chen  wrote:
>>
>> Here's a quick run down on the change:
>>  https://forums.freebsd.org/threads/52871/
>>
>> The portconf features have been baked into the ports system, and you
>> can set/unset options within /etc/make.conf, eg:
>>
>> graphics_atril_SET=DVI T1LIB
>> mail_thunderbird_UNSET= PULSEAUDIO
>
> Out of curiosity, is there a global way to disable X11 (say) in this? Is that 
> documented anywhere?
>
> In portconf, I was able to add a line:
>
> *: WITHOUT_X11=“YES”
>
> and it would (hopefully) suppress X11. Do I need to add
>
> port_UNSET= X11
>
> for every port that will get installed?

Try:
OPTIONS_UNSET= X11

Multiple options can also be set, eg:
OPTIONS_UNSET= X11 NLS DOCS

Cheers.
-- 
Jonathan Chen 
___
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: Configuring options/knobs without `make config`

2017-07-31 Thread Morse, Richard E.,MGH
On Jul 31, 2017, at 4:06 PM, Jonathan Chen  wrote:
> 
> Here's a quick run down on the change:
>  https://forums.freebsd.org/threads/52871/
> 
> The portconf features have been baked into the ports system, and you
> can set/unset options within /etc/make.conf, eg:
> 
> graphics_atril_SET=DVI T1LIB
> mail_thunderbird_UNSET= PULSEAUDIO

Out of curiosity, is there a global way to disable X11 (say) in this? Is that 
documented anywhere?

In portconf, I was able to add a line:

*: WITHOUT_X11=“YES”

and it would (hopefully) suppress X11. Do I need to add

port_UNSET= X11

for every port that will get installed?

Ricky


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
___
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: Configuring options/knobs without `make config`

2017-07-31 Thread Jonathan Chen
On 1 August 2017 at 07:50, Morse, Richard E.,MGH
 wrote:
> Hi! I used to use portconf on the machine this is going to be replacing, but 
> it seemed like there were changes to the way the port system worked between 
> 8.4 and 11, and I couldn’t find anything that documented how to properly set 
> up portconf for the new “options” stuff, in place of the old “WITH/WITHOUT” 
> stuff. Can you recommend somewhere I can find that out?
>

Here's a quick run down on the change:
  https://forums.freebsd.org/threads/52871/

The portconf features have been baked into the ports system, and you
can set/unset options within /etc/make.conf, eg:

graphics_atril_SET=DVI T1LIB
mail_thunderbird_UNSET= PULSEAUDIO

Cheers.
-- 
Jonathan Chen 
___
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: Configuring options/knobs without `make config`

2017-07-31 Thread Morse, Richard E.,MGH
Hi! I used to use portconf on the machine this is going to be replacing, but it 
seemed like there were changes to the way the port system worked between 8.4 
and 11, and I couldn’t find anything that documented how to properly set up 
portconf for the new “options” stuff, in place of the old “WITH/WITHOUT” stuff. 
Can you recommend somewhere I can find that out?

Thanks,
Ricky

> On Jul 27, 2017, at 8:18 PM, Dewayne Geraghty 
>  wrote:
> 
> Richard,
> I'm unsure of how you're planning on using the information, perhaps
> these suggestions may help:
> 
> To examine what options are available, chosen or rejected (note: the
> value of CATEGORY and PORT must be in lowercase):
> make -C /usr/ports/$CATEGORY/$PORT -VPORT_OPTIONS -VSELECTED_OPTIONS
> -VDESELECTED_OPTIONS
> 
> If you're after consistency, then I would suggest that you use
> /etc/make.conf to ascribe the options that you want for each of the ports.
> 
> For example, using mail/dovecot2:
> mail_dovecot2_SET=LZ4 KQUEUE SSL
> mail_dovecot2_UNSET=BDB PGSQL
> 
> I'll reiterate that I don't interactively set port options on anything,
> so no "make config".  I use a tool called ports-mgmt/portconf to manage
> my ports. I can't recommend the tool as I do some preprocessing to align
> with port devs requirements, currently
> $CATEGORY_$PORT_[SET|UNSET]=
> if in /etc/make.conf or on the command line by
> [WITH|WITHOUT]=
> 
> Enjoy.
> Dewayne



The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
___
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: Configuring options/knobs without `make config`

2017-07-28 Thread Chris Rees

___
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: Configuring options/knobs without `make config`

2017-07-27 Thread Thomas Mueller
from Kevin Oberman:

> On Thu, Jul 27, 2017 at 7:36 AM, Morse, Richard E.,MGH <
> remo...@mgh.harvard.edu> wrote:

> > Hi! I’m trying to document the setup of a new system, and I’m finding it
> > really complicated to document exactly which options I choose for various
> > ports.

> > I was wondering if there is some magic command-line syntax, (ideally to
> > postmaster) that would let me document the options selected in the form of
> > a command — something like:

> > postmaster editors/vim -o NOLUA,NOPYTHON,NORUBY,CONSOLE,NOGNOME

> > (to indicate the changes from the default settings; I would be fine if I
> > had to specify every option, I suppose, but ideally only ones that 
> > changed…)

> > Thanks,
> > Ricky

> Short answer is "no". because the ports system always remembers teh chosen
> configuration for any port and that is stored in the pkg database, I am not
> aware of any tool that allows setting of options from the command line.
> That said, it is certainly possible and does not look difficult to
> implement. It would probably be both easiest and more supportable to set
> the options in the command line into the DB. Of course, '-o' is already in
> use, so that would net be available.

> More difficult to deal with is the issue of default options. Frankly, that
> is not an issue that is really handled at all well with any of the current
> tools and periodically bites my in the ass. Clearly, requiring all options
> to e listed on the command line is not workable. (Just look at the list of
> options on some multimedia ports.) So the assumption is that the command
> line only specifies variations from defaults, but that does not address how
> to deal with changes in defaults or with deleted options. I don't have
> obvious answers on this. Do you? It's certainly not trivial.

> As a non-answer to your question, maybe a dump of the current options. That
> could easily be added to most any tool ad it is a one-line command.
> make -C PORT_PATH showconfig
> where "PORT_PATH" is the path to the port, e.g.
> /usr/ports/multimedia/ffmpeg. It could easily in a simple wrapper around
> some other command such as portmaster.

> Maybe someone else has a better idea, but it does not look at all simple to 
> me.

NetBSD with pkgsrc, and Gentoo portage have no options dialog; options are put 
in mk.conf or make.conf : much easier to deal with.

Dialog4ports is a big improvement over the old options dialog which generally 
messed up the screen.  I had to, and still have to, run "make config-recursive" 
several times because something new would show up on the second run and 
possibly further runs of "make config-recursive".

It's nice to have something like

PKG_DEFAULT_OPTIONS+= ssl inet6 nls ncurses pcre gtk3 x11 fftw esound cups 
sndfile

and

PKG_OPTIONS.msmtp+= idn 
PKG_OPTIONS.w3m+= w3m-image-gtk2
PKG_OPTIONS.gcc-aux+= testsuite

or USE= ... in Gentoo with portage.

Is there any way to achieve something like that with FreeBSD using ports?

It would be a big nuisance to have to put all nondefault options on the command 
line with portmaster, and a bigger nuisance when building or updating many 
ports with a single portmaster command.

Tom

___
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: Configuring options/knobs without `make config`

2017-07-27 Thread Dewayne Geraghty
Oops.  I forgot to mention that you would use portmaster this way
/usr/local/sbin/portmaster -m "commands to pass" $CATEGORY/$PORT
which I use for other tasks, as explained earlier.
For example
portmaster -m 'WITH="SQLITE LDAP" WITHOUT="DIGEST IPV6"' $CAT/$PORT

Note: -m "" can not be issued multiple times on the command line.

___
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: Configuring options/knobs without `make config`

2017-07-27 Thread Dewayne Geraghty
Richard,
I'm unsure of how you're planning on using the information, perhaps
these suggestions may help:

To examine what options are available, chosen or rejected (note: the
value of CATEGORY and PORT must be in lowercase):
make -C /usr/ports/$CATEGORY/$PORT -VPORT_OPTIONS -VSELECTED_OPTIONS
-VDESELECTED_OPTIONS

If you're after consistency, then I would suggest that you use
/etc/make.conf to ascribe the options that you want for each of the ports.

For example, using mail/dovecot2:
mail_dovecot2_SET=LZ4 KQUEUE SSL
mail_dovecot2_UNSET=BDB PGSQL

I'll reiterate that I don't interactively set port options on anything,
so no "make config".  I use a tool called ports-mgmt/portconf to manage
my ports. I can't recommend the tool as I do some preprocessing to align
with port devs requirements, currently
$CATEGORY_$PORT_[SET|UNSET]=
if in /etc/make.conf or on the command line by
[WITH|WITHOUT]=

Enjoy.
Dewayne
___
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: Configuring options/knobs without `make config`

2017-07-27 Thread Kevin Oberman
On Thu, Jul 27, 2017 at 7:36 AM, Morse, Richard E.,MGH <
remo...@mgh.harvard.edu> wrote:

> Hi! I’m trying to document the setup of a new system, and I’m finding it
> really complicated to document exactly which options I choose for various
> ports.
>
> I was wondering if there is some magic command-line syntax, (ideally to
> postmaster) that would let me document the options selected in the form of
> a command — something like:
>
> postmaster editors/vim -o NOLUA,NOPYTHON,NORUBY,CONSOLE,NOGNOME
>
> (to indicate the changes from the default settings; I would be fine if I
> had to specify every option, I suppose, but ideally only ones that changed…)
>
> Thanks,
> Ricky
>
>
Short answer is "no". because the ports system always remembers teh chosen
configuration for any port and that is stored in the pkg database, I am not
aware of any tool that allows setting of options from the command line.
That said, it is certainly possible and does not look difficult to
implement. It would probably be both easiest and more supportable to set
the options in the command line into the DB. Of course, '-o' is already in
use, so that would net be available.

More difficult to deal with is the issue of default options. Frankly, that
is not an issue that is really handled at all well with any of the current
tools and periodically bites my in the ass. Clearly, requiring all options
to e listed on the command line is not workable. (Just look at the list of
options on some multimedia ports.) So the assumption is that the command
line only specifies variations from defaults, but that does not address how
to deal with changes in defaults or with deleted options. I don't have
obvious answers on this. Do you? It's certainly not trivial.

As a non-answer to your question, maybe a dump of the current options. That
could easily be added to most any tool ad it is a one-line command.
make -C PORT_PATH showconfig
where "PORT_PATH" is the path to the port, e.g.
/usr/ports/multimedia/ffmpeg. It could easily in a simple wrapper around
some other command such as portmaster.

Maybe someone else has a better idea, but it does not look at all simple to
me.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"

Configuring options/knobs without `make config`

2017-07-27 Thread Morse, Richard E.,MGH
Hi! I’m trying to document the setup of a new system, and I’m finding it really 
complicated to document exactly which options I choose for various ports.

I was wondering if there is some magic command-line syntax, (ideally to 
postmaster) that would let me document the options selected in the form of a 
command — something like:

postmaster editors/vim -o NOLUA,NOPYTHON,NORUBY,CONSOLE,NOGNOME

(to indicate the changes from the default settings; I would be fine if I had to 
specify every option, I suppose, but ideally only ones that changed…)

Thanks,
Ricky


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
___
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"