Re: Synth and circular dependencies

[Thomas Mueller]

> On 31 August 2017 at 17:59, Thomas Mueller  wrote:
> > Now I've been busy, selecting port options to include in
> > /usr/local/etc/synth/LiveSystem-make.conf

> > but when I run "synth status gnumeric", I get

> > Configuration invalid: [D] Port options directory: /var/db/ports

> > so without a directory like /var/db/ports showing options derived from the 
> > ports dialog, synth seems not to work.

> The directory *must* be there, but it can be empty.

> > Is there any dialog-free way to use synth?

> Yup, I'm using it with the LiveSystem-make.conf.

> Cheers.

> Jonathan Chen 

I tried setting the port options directory to 
/usr/local/etc/synth/LiveSystem-make.conf, but I guess that was not good enough.

Maybe it had to be a directory, not a file?

I will try again when I get back into that installation.

I also wonder about the future of synth with John Marino banished from FreeBSD, 
don't want to go to DragonFlyBSD because of incompatibility problems not 
relating to dports.

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: Synth and circular dependencies

[Jonathan Chen]

On 31 August 2017 at 17:59, Thomas Mueller  wrote:
> Now I've been busy, selecting port options to include in
> /usr/local/etc/synth/LiveSystem-make.conf
>
> but when I run "synth status gnumeric", I get
>
> Configuration invalid: [D] Port options directory: /var/db/ports
>
> so without a directory like /var/db/ports showing options derived from the 
> ports dialog, synth seems not to work.

The directory *must* be there, but it can be empty.

> Is there any dialog-free way to use synth?

Yup, I'm using it with the LiveSystem-make.conf.

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: Synth and circular dependencies

[Thomas Mueller]

Now I've been busy, selecting port options to include in 
/usr/local/etc/synth/LiveSystem-make.conf

but when I run "synth status gnumeric", I get

Configuration invalid: [D] Port options directory: /var/db/ports

so without a directory like /var/db/ports showing options derived from the 
ports dialog, synth seems not to work.

Is there any dialog-free way to use synth?

Synth has been ported to pkgsrc where there is no dialog, so maybe there is a 
way?

Or maybe synth does not run with pkgsrc?  Synth seems to be falling into 
desuetude there.

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: Synth and circular dependencies

[Thomas Mueller]

> > Does synth look for options in /etc/make.conf, or only in 
> > /usr/local/etc/synth/LiveSystem-make.conf ?

> synth doesn't look at /etc/make.conf. When it is building, it uses the
> options from /usr/local/etc/synth/LiveSystem-make.conf.

> > From "man synth"
>
> >  Port options directoryThis is the directory where all the selected
> >options for ports are cached.  The initial
> >value comes from a system scan, so chances 
> > are
> >it has the correct value. However, if the 
> > user
> >would like a separate configuration area for
> >port options, they would create the new 
> > direc-
> >tory and set this value accordingly (but the
> >user would have to ensure the new location is
> >passed to the port when configuring port
> >options later in that case).
>
> > Do the options have to be in /var/db/ports format, which I want to avoid at 
> > all cost?  Or is the LiveSystem-make.conf and /etc/make.conf good enough?

> synth will inspect the specified ports-options directory for options
> in /var/db/ports format. This allows new users to immediately use
> synth without having to configure anything.

> > Just to see what would happen, I don't think I need to run "synth 
> > upgrade-system".  "synth status" might be good enough.

> Yup, you're right.

> Cheers.

> Jonathan Chen 

So I should put the options in /usr/local/etc/synth/LiveSystem-make.conf .  I 
could also put options in /etc/make.conf just in case I build something with 
other than synth ("make install clean").

I guess I'll get the chance to see what happens when the port options directory 
is not there.  Hopefully it won't find /var/db/ports2 if I don't tell it.

from Don Lewis:

> On 23 Aug, Thomas Mueller wrote:

> > But it seems more cumbersome with "make PORT_DBDIR=... showconfig"
> > than with "make show-options" and "make show depends-options" in
> > NetBSD with pkgsrc.  Or maybe I'm spoiled?

> PORT_DBDIR= only needs to be specified if you want to point to somewhere
> other than the default location.  Otherwise just "make showconfig" will
> suffice.

I tried 
make PORT_DBDIR=(nonexistent directory) showconfig
and it worked.

Maybe it acted based on default options?

I could try 

make PORT_DBDIR=(real or nonexistent directory) showconfig-recursive |& tee 
showconfigrecursive.log (or maybe a shorter name)  

comparable to

make show-depends-options 2>&1 | tee optionsdep.log  in NetBSD with pkgsrc

I really need the options to have better visibility than /var/db/ports offers.


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: Synth and circular dependencies

[Don Lewis]

On 23 Aug, Thomas Mueller wrote:

> But it seems more cumbersome with "make PORT_DBDIR=... showconfig"
> than with "make show-options" and "make show depends-options" in
> NetBSD with pkgsrc.  Or maybe I'm spoiled?

PORT_DBDIR= only needs to be specified if you want to point to somewhere
other than the default location.  Otherwise just "make showconfig" will
suffice.

___
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: Synth and circular dependencies

[Jonathan Chen]

On 24 August 2017 at 11:12, Thomas Mueller  wrote:
>> > I can run "synth status ..." on desired packages to see before running if 
>> > the options are compatible.
>
>> My 2 cents worth: the port maintainers usually do a good job of
>> choosing sensible default options. I would just move everything out of
>> /var/db/ports/ and see what a "synth upgrade-system" comes back with.
>> My LiveSystem-make.conf only contains a handful of lines where I
>> disagree with the port maintainers' choices.
>
>> Cheers.
>
>> Jonathan Chen 
>
> I could start from scratch on the options but not deleting packages already 
> installed.
>
> But it seems more cumbersome with "make PORT_DBDIR=... showconfig" than with 
> "make show-options" and "make show depends-options" in NetBSD with pkgsrc.  
> Or maybe I'm spoiled?
>
> Does synth look for options in /etc/make.conf, or only in 
> /usr/local/etc/synth/LiveSystem-make.conf ?

synth doesn't look at /etc/make.conf. When it is building, it uses the
options from /usr/local/etc/synth/LiveSystem-make.conf.

> From "man synth"
>
>  Port options directoryThis is the directory where all the selected
>options for ports are cached.  The initial
>value comes from a system scan, so chances are
>it has the correct value. However, if the user
>would like a separate configuration area for
>port options, they would create the new direc-
>tory and set this value accordingly (but the
>user would have to ensure the new location is
>passed to the port when configuring port
>options later in that case).
>
> Do the options have to be in /var/db/ports format, which I want to avoid at 
> all cost?  Or is the LiveSystem-make.conf and /etc/make.conf good enough?

synth will inspect the specified ports-options directory for options
in /var/db/ports format. This allows new users to immediately use
synth without having to configure anything.

> Just to see what would happen, I don't think I need to run "synth 
> upgrade-system".  "synth status" might be good enough.

Yup, you're right.

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: Synth and circular dependencies

[Thomas Mueller]

> > I can run "synth status ..." on desired packages to see before running if 
> > the options are compatible.

> My 2 cents worth: the port maintainers usually do a good job of
> choosing sensible default options. I would just move everything out of
> /var/db/ports/ and see what a "synth upgrade-system" comes back with.
> My LiveSystem-make.conf only contains a handful of lines where I
> disagree with the port maintainers' choices.

> Cheers.

> Jonathan Chen 

I could start from scratch on the options but not deleting packages already 
installed.

But it seems more cumbersome with "make PORT_DBDIR=... showconfig" than with 
"make show-options" and "make show depends-options" in NetBSD with pkgsrc.  Or 
maybe I'm spoiled?

Does synth look for options in /etc/make.conf, or only in 
/usr/local/etc/synth/LiveSystem-make.conf ?

>From "man synth"

 Port options directoryThis is the directory where all the selected
   options for ports are cached.  The initial
   value comes from a system scan, so chances are
   it has the correct value. However, if the user
   would like a separate configuration area for
   port options, they would create the new direc-
   tory and set this value accordingly (but the
   user would have to ensure the new location is
   passed to the port when configuring port
   options later in that case).

Do the options have to be in /var/db/ports format, which I want to avoid at all 
cost?  Or is the LiveSystem-make.conf and /etc/make.conf good enough?

Just to see what would happen, I don't think I need to run "synth 
upgrade-system".  "synth status" might be good enough.

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: Synth and circular dependencies

[Jonathan Chen]

On 23 August 2017 at 18:20, Thomas Mueller  wrote:
[...]
> I can try the script or start over from the beginning given the mess I got 
> into.
>
> But the complexity of the script convinces me further of how dialog-free 
> systems (pkgsrc, Gentoo portage for instance) are better.
>
> But I was going strong with synth, and that might encourage me to continue to 
> make that installation more fully functional.
>
> I can run "synth status ..." on desired packages to see before running if the 
> options are compatible.

My 2 cents worth: the port maintainers usually do a good job of
choosing sensible default options. I would just move everything out of
/var/db/ports/ and see what a "synth upgrade-system" comes back with.
My LiveSystem-make.conf only contains a handful of lines where I
disagree with the port maintainers' choices.

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: Synth and circular dependencies

[Thomas Mueller]

from Don Lewis:

> When I switched from portupgrade to poudriere, I used the attached
> script to find the non-default option settings in /var/db/ports.


> [-- Attachment #2: portoptions --]
> [-- Type: text/plain, Encoding: 7bit, Size: 1.4K --]
> Content-Type: TEXT/plain; name=portoptions
> Content-Disposition: attachment; filename=portoptions

> #!/bin/sh
> PORTSDIR=/usr/ports
(snip)

Thanks for the script, I assume I can modify PORTSDIR line as needed.

No need to quote all, especially with "> " prepended to each line.

I can try the script or start over from the beginning given the mess I got into.

But the complexity of the script convinces me further of how dialog-free 
systems (pkgsrc, Gentoo portage for instance) are better.

But I was going strong with synth, and that might encourage me to continue to 
make that installation more fully functional.

I can run "synth status ..." on desired packages to see before running if the 
options are compatible.

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: Synth and circular dependencies

[Adam Weinberger]

> On 22 Aug, 2017, at 20:11, Thomas Mueller  wrote:
> 
> from Jonathan Chen:
> 
>> On 22 August 2017 at 18:34, Thomas Mueller  wrote:
> [...]
>>> I believe Synth and poudriere have no means for setting options.  That 
>>> should be enough impetus to make it easier to bypass the dialog4ports 
>>> entirely.
> 
>>> From the synth man page:
>> -make.conf
>>   This is an optional, user-provided file. If it exists,
>>   the builder's /etc/make.conf will be appended with the
>>   contents of this file. For the default profile, the
>>   file would normally be located at
>>   /usr/local/etc/synth/LiveSystem-make.conf
> 
>> All you need to do is to convert your /var/db/ports/* options into
>> make.conf style options and put it into LiveSystem-make.conf.
> 
>> Works for me.
> 
> At this stage, I think I don't want to ever again see a dialog4ports!
> 
> How do I convert /var/db/ports/* options into make.conf-style options in a 
> reasonable amount of time?

Make a script. The directory name is the option prefix.

> I don't (yet) have a LiveSystem-make.conf apart from /etc/make.conf, but I 
> have 
> /usr/local/etc/synth/synth.ini
> 
> I see (running "less" on this file)
> 
> [Global Configuration]
> 
> 
> [LiveSystem]
> 
> Directory_packages= /var/synth/live_packages
> Directory_repository= /var/synth/live_packages/All
> Directory_portsdir= /BETA1/usr/ports
> Directory_options= /var/db/ports
> Directory_distfiles= /BETA1/usr/ports/distfiles
> Directory_buildbase= /usr/obj/synth-live
> Directory_logs= /var/log/synth
> Directory_ccache= disabled
> Directory_system= /
> Number_of_builders= 6
> Max_jobs_per_builder= 4
> Tmpfs_workdir= true
> Tmpfs_localbase= true
> Display_with_ncurses= true
> leverage_prebuilt= false
> 
> occurring four times, the latter three being verbatim repeats of the first.
> 
> Now I want to get rid of the Directory_options line, should I delete the line 
> or should I change "/var/db/ports" to "/dev/null"?  Or just move 
> /var/db/ports to /var/db/ports2, which I intend to do anyway?
> 
> What if synth finds /var/db/ports no longer there?

Just move everything out of it. That directory starts off empty anyway.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.org

___
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: Synth and circular dependencies

[Thomas Mueller]

from Jonathan Chen:

> On 22 August 2017 at 18:34, Thomas Mueller  wrote:
[...]
> > I believe Synth and poudriere have no means for setting options.  That 
> > should be enough impetus to make it easier to bypass the dialog4ports 
> > entirely.

> >From the synth man page:
>  -make.conf
>This is an optional, user-provided file. If it exists,
>the builder's /etc/make.conf will be appended with the
>contents of this file. For the default profile, the
>file would normally be located at
>/usr/local/etc/synth/LiveSystem-make.conf

> All you need to do is to convert your /var/db/ports/* options into
> make.conf style options and put it into LiveSystem-make.conf.

> Works for me.

At this stage, I think I don't want to ever again see a dialog4ports!

How do I convert /var/db/ports/* options into make.conf-style options in a 
reasonable amount of time?

I don't (yet) have a LiveSystem-make.conf apart from /etc/make.conf, but I have 
/usr/local/etc/synth/synth.ini

I see (running "less" on this file)

[Global Configuration]


[LiveSystem]

Directory_packages= /var/synth/live_packages
Directory_repository= /var/synth/live_packages/All
Directory_portsdir= /BETA1/usr/ports
Directory_options= /var/db/ports
Directory_distfiles= /BETA1/usr/ports/distfiles
Directory_buildbase= /usr/obj/synth-live
Directory_logs= /var/log/synth
Directory_ccache= disabled
Directory_system= /
Number_of_builders= 6
Max_jobs_per_builder= 4
Tmpfs_workdir= true
Tmpfs_localbase= true
Display_with_ncurses= true
leverage_prebuilt= false

occurring four times, the latter three being verbatim repeats of the first.

Now I want to get rid of the Directory_options line, should I delete the line 
or should I change "/var/db/ports" to "/dev/null"?  Or just move /var/db/ports 
to /var/db/ports2, which I intend to do anyway?

What if synth finds /var/db/ports no longer there?

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: Synth and circular dependencies

[Jonathan Chen]

On 22 August 2017 at 18:34, Thomas Mueller  wrote:
[...]
> I believe Synth and poudriere have no means for setting options.  That should 
> be enough impetus to make it easier to bypass the dialog4ports entirely.

>From the synth man page:
 -make.conf
   This is an optional, user-provided file. If it exists,
   the builder's /etc/make.conf will be appended with the
   contents of this file. For the default profile, the
   file would normally be located at
   /usr/local/etc/synth/LiveSystem-make.conf

All you need to do is to convert your /var/db/ports/* options into
make.conf style options and put it into LiveSystem-make.conf.

Works for me.
-- 
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: Synth and circular dependencies

[Thomas Mueller]

from RW via freebsd-ports:

> Thomas Mueller wrote:


> > It was very disconcerting when I would do a massive portupgrade
> > before going to bed and subsequently find portupgrade stopped for an
> > options dialog.

> FWIW portupgrade has a -c option to avoid that.

I remember that back from the days when I used portupgrade, and ports system 
used the old dialog.

I wish NetBSD and pkgsrc would port portmaster and/or portupgrade.

Synth and pkgng seem to have fallen into desuetude in pkgsrc. 

Synth won't build on NetBSD because gcc6-aux is broken (Makefile says so), and 
I failed in an attempt to build pkg on NetBSD, but good on FreeBSD ports.

from Don Lewis and my previous post:

> > What is the priority when /var/db/ports is present, which takes
> > precedence?  Should I delete /var/db/ports or /var/db/ports/* ?

> I suspect that /var/db/ports takes priority of options are set in both
> places.  I'd delete it if you move your option settings to make.conf.

> > The ports dialog prior to dialog4ports would always mess the screen
> > whenever I made a log file with tee (just as bad with script).
> > Dialog4ports avoided messing the screen.
>
> > It was very disconcerting when I would do a massive portupgrade before
> > going to bed and subsequently find portupgrade stopped for an options
> > dialog.
 
> I always ran "portupgrade -aFc" beforehand to set the options and also
> fetch all the distfiles.  Some of the ports that I built had distfiles
> that needed to be manually fetched and a fetch failure during the night
> could also be devastating.  Even then there was one port that had its
> own dialog (procmail?) that would sometimes wedge an overnight
> portupgrade run.
 
> > I believe Synth and poudriere have no means for setting options.  That
> > should be enough impetus to make it easier to bypass the dialog4ports
> > entirely.

> The poudriere testport -c option runs make config to pop up the options
> dialog.  It's handy for testing the port's options when doing
> development.  The options settings aren't sticky, though.

> > (NetBSD) pkgsrc has a file options.mk in each package entry where
> > there are options.  One can run "make show-options" and "make
> > show-depends-options" to see options for main package and
> > dependencies.  I like it better than "make showconfig-recursive".
>
> > Now for FreeBSD 11.1-STABLE installation, I will have to redo the
> > options into OPTIONS_SET, etc, and either delete /var/db/ports (a
> > horrible mess now, so nothing to lose) or move it out of the way.
>
> > Another advantage of putting options in make.conf or mk.conf is that
> > the file can be copied or edited from another FreeBSD or NetBSD
> > installation.

> Well, you could copy /var/db/ports over, but ...

If I want to partially convert options from /var/db/ports but keep out of 
harm's way, I could move it to /var/db/ports2 for reference.

Then I could 
make PORT_DBDIR=/var/db/ports2 showconfig-recursive
or from another installation, mounting on /media/zip0,
make PORT_DBDIR=/media/zip0/var/db/ports2 showconfig-recursive

Or I could look directly in /var/db/ports2 files (cumbersome), that would even 
work from NetBSD.

I no longer use traditional BSD disklabels, so, with GPT, FreeBSD and NetBSD 
can read and write each other's ffs/UFS partitions.

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: Synth and circular dependencies

[Don Lewis]

On 22 Aug, Thomas Mueller wrote:
> from Jonathan Chen:
> 
>> On 22 August 2017 at 15:17, Thomas Mueller
>>  wrote:
> [...]
>> > I really need to be able to see the options in a better way than
>> > the FreeBSD ports framework allows, like in a file /etc/mk.conf
>> > (pkgsrc) or USE= ... as in /etc/make.conf (Gentoo portage).
> 
>> > Dialog4ports is better than the previous dialog but not as good as
>> > seeing in a file mk.conf or make.conf .
> 
>> > Otherwise, I don't really know any elegant way to fix the options
>> > mess I got into.
> 
>> Any reason why don't you can't all your options into /etc/make.conf?
>> I've never used /var/db/ports options as they're not easy to review
>> in one go.
> 
> Going through /var/db/ports is a recipe for insanity.
> 
> from Don Lewis:
> 
>> It is possible to set the options for ports in /etc/make.conf.  That
>> is how I handle it would poudriere which looks for make.conf files in
>> /usr/local/etc/poudriere.d and can use make.conf files that are
>> specific to each jail, ports tree and ports set (poudriere -z option
>> to specify the latter).
> 
>> Specifying the options in make.conf also makes it easier to set
>> options globally for all all of the ports that you build so they are
>> consistent. For instance I specify these options globally:
> 
>> OPTIONS_SET=CUPS APPLET OPENBLAS OBLAS SZIP LETTER GUILE2 GSSAPI_NONE
>> KRB_NONE OPTIONS_UNSET=GUILE1 NETLIB REFERENCE GSSAPI_BASE KRB_BASE
>> KERBEROS
> 
>> Port-specific options can be set like this:
> 
>> graphics_gimp-help_SET=EN
>> graphics_gimp-help_UNSET=ALL
> 
>> Back when I still used portupgrade, I found that dialog4ports got to
>> be really frustrating.
> 
> What is the priority when /var/db/ports is present, which takes
> precedence?  Should I delete /var/db/ports or /var/db/ports/* ?

I suspect that /var/db/ports takes priority of options are set in both
places.  I'd delete it if you move your option settings to make.conf.

> The ports dialog prior to dialog4ports would always mess the screen
> whenever I made a log file with tee (just as bad with script). 
> Dialog4ports avoided messing the screen.
> 
> It was very disconcerting when I would do a massive portupgrade before
> going to bed and subsequently find portupgrade stopped for an options
> dialog.

I always ran "portupgrade -aFc" beforehand to set the options and also
fetch all the distfiles.  Some of the ports that I built had distfiles
that needed to be manually fetched and a fetch failure during the night
could also be devastating.  Even then there was one port that had its
own dialog (procmail?) that would sometimes wedge an overnight
portupgrade run.

> I believe Synth and poudriere have no means for setting options.  That
> should be enough impetus to make it easier to bypass the dialog4ports
> entirely.

The poudriere testport -c option runs make config to pop up the options
dialog.  It's handy for testing the port's options when doing
development.  The options settings aren't sticky, though.

> (NetBSD) pkgsrc has a file options.mk in each package entry where
> there are options.  One can run "make show-options" and "make
> show-depends-options" to see options for main package and
> dependencies.  I like it better than "make showconfig-recursive".
> 
> Now for FreeBSD 11.1-STABLE installation, I will have to redo the
> options into OPTIONS_SET, etc, and either delete /var/db/ports (a
> horrible mess now, so nothing to lose) or move it out of the way.
> 
> Another advantage of putting options in make.conf or mk.conf is that
> the file can be copied or edited from another FreeBSD or NetBSD
> installation.

Well, you could copy /var/db/ports over, but ...

___
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: Synth and circular dependencies

[RW via freebsd-ports]

On Tue, 22 Aug 2017 06:34:15 +
Thomas Mueller wrote:


> It was very disconcerting when I would do a massive portupgrade
> before going to bed and subsequently find portupgrade stopped for an
> options dialog. 

FWIW portupgrade has a -c option to avoid that.
 
___
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: Synth and circular dependencies

[Don Lewis]

On 21 Aug, To: mueller6...@bellsouth.net wrote:
> On 22 Aug, Thomas Mueller wrote:
>> Again, I am responding from the FreeBSD mailing list web interface
>> because that is faster than reaching my inbox.
>> 
>> from Don Lewis truckman at FreeBSD.org
>> Mon Aug 21 23:16:36 UTC 2017
>> 
>>> > I went to /usr/ports/textproc/xmlto , ran "make all-depends-list",
>>> > and one line that showed up was
>>> > /usr/ports/textproc/xmlto
>>  
>>> > depends on itself.
>> 
>>> I don't see that here with default option settings:
>> 
>>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>>> textproc
>>> /usr/ports/textproc/libxml2
>>> /usr/ports/textproc/libxslt
>>> /usr/ports/textproc/docbook-xsl
>>> /usr/ports/textproc/xmlcatmgr
>>> /usr/ports/textproc/docbook
>>> /usr/ports/textproc/docbook-sgml
>>> /usr/ports/textproc/iso8879
>>> /usr/ports/textproc/docbook-xml
>>> /usr/ports/textproc/xmlcharent
>>> /usr/ports/textproc/sdocbook-xml
>> 
>>> > Otherwise, on newer system, I see circular dependencies running
>>> > "make all-depends-list", finding textproc/xmlto depended on
>>> > graphics/gd and vice versa.
>> 
>>> I don't see the former:
>> 
>>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>>> graphics
>>> [nada]
>> 
>>> or the latter:
>> 
>>> %cd /usr/ports/graphics/gd && make all-depends-list | grep textproc 
>>> /usr/ports/textproc/expat2
>> 
>>> This is with the head branch of the ports tree, revision r448344.
>> 
>>> Problems like this with the default option settings tend to get found
>>> and fixed fairly quickly because this will cause failures on the
>>> package build cluster and will spam the maintainer's mailbox with
>>> build failure messages.
>> 
>> I didn't think I went overboard selecting options, but I did want
>> documentation.  Maybe that screwed up, or the ports tree was not up to
>> it.
>> 
>> I suppose I could move (mv) /var/db/ports to /var/db/ports2
>> temporarily just to see what happens when I "make all-depends-list".
>> 
>> I really need to be able to see the options in a better way than the
>> FreeBSD ports framework allows, like in a file /etc/mk.conf (pkgsrc)
>> or USE= ... as in /etc/make.conf (Gentoo portage).
>>
>> Dialog4ports is better than the previous dialog but not as good as
>> seeing in a file mk.conf or make.conf .
> 
> 
> It is possible to set the options for ports in /etc/make.conf.  That is
> how I handle it would poudriere which looks for make.conf files in

s/would/with/

> /usr/local/etc/poudriere.d and can use make.conf files that are specific
> to each jail, ports tree and ports set (poudriere -z option to specify
> the latter).
> 
> Specifying the options in make.conf also makes it easier to set options
> globally for all all of the ports that you build so they are consistent.
> For instance I specify these options globally:
> 
> OPTIONS_SET=CUPS APPLET OPENBLAS OBLAS SZIP LETTER GUILE2 GSSAPI_NONE KRB_NONE
> OPTIONS_UNSET=GUILE1 NETLIB REFERENCE GSSAPI_BASE KRB_BASE KERBEROS
> 
> Port-specific options can be set like this:
> 
> graphics_gimp-help_SET=EN
> graphics_gimp-help_UNSET=ALL
> 
> Back when I still used portupgrade, I found that dialog4ports got to be
> really frustrating.
> 
> ___
> 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"

___
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: Synth and circular dependencies

[Don Lewis]

On 22 Aug, Thomas Mueller wrote:
> Again, I am responding from the FreeBSD mailing list web interface
> because that is faster than reaching my inbox.
> 
> from Don Lewis truckman at FreeBSD.org
> Mon Aug 21 23:16:36 UTC 2017
> 
>> > I went to /usr/ports/textproc/xmlto , ran "make all-depends-list",
>> > and one line that showed up was
>> > /usr/ports/textproc/xmlto
>  
>> > depends on itself.
> 
>> I don't see that here with default option settings:
> 
>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>> textproc
>> /usr/ports/textproc/libxml2
>> /usr/ports/textproc/libxslt
>> /usr/ports/textproc/docbook-xsl
>> /usr/ports/textproc/xmlcatmgr
>> /usr/ports/textproc/docbook
>> /usr/ports/textproc/docbook-sgml
>> /usr/ports/textproc/iso8879
>> /usr/ports/textproc/docbook-xml
>> /usr/ports/textproc/xmlcharent
>> /usr/ports/textproc/sdocbook-xml
> 
>> > Otherwise, on newer system, I see circular dependencies running
>> > "make all-depends-list", finding textproc/xmlto depended on
>> > graphics/gd and vice versa.
> 
>> I don't see the former:
> 
>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>> graphics
>> [nada]
> 
>> or the latter:
> 
>> %cd /usr/ports/graphics/gd && make all-depends-list | grep textproc 
>> /usr/ports/textproc/expat2
> 
>> This is with the head branch of the ports tree, revision r448344.
> 
>> Problems like this with the default option settings tend to get found
>> and fixed fairly quickly because this will cause failures on the
>> package build cluster and will spam the maintainer's mailbox with
>> build failure messages.
> 
> I didn't think I went overboard selecting options, but I did want
> documentation.  Maybe that screwed up, or the ports tree was not up to
> it.
> 
> I suppose I could move (mv) /var/db/ports to /var/db/ports2
> temporarily just to see what happens when I "make all-depends-list".
> 
> I really need to be able to see the options in a better way than the
> FreeBSD ports framework allows, like in a file /etc/mk.conf (pkgsrc)
> or USE= ... as in /etc/make.conf (Gentoo portage).
>
> Dialog4ports is better than the previous dialog but not as good as
> seeing in a file mk.conf or make.conf .


It is possible to set the options for ports in /etc/make.conf.  That is
how I handle it would poudriere which looks for make.conf files in
/usr/local/etc/poudriere.d and can use make.conf files that are specific
to each jail, ports tree and ports set (poudriere -z option to specify
the latter).

Specifying the options in make.conf also makes it easier to set options
globally for all all of the ports that you build so they are consistent.
For instance I specify these options globally:

OPTIONS_SET=CUPS APPLET OPENBLAS OBLAS SZIP LETTER GUILE2 GSSAPI_NONE KRB_NONE
OPTIONS_UNSET=GUILE1 NETLIB REFERENCE GSSAPI_BASE KRB_BASE KERBEROS

Port-specific options can be set like this:

graphics_gimp-help_SET=EN
graphics_gimp-help_UNSET=ALL

Back when I still used portupgrade, I found that dialog4ports got to be
really frustrating.

___
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: Synth and circular dependencies

[Jonathan Chen]

On 22 August 2017 at 15:17, Thomas Mueller  wrote:
[...]
> I really need to be able to see the options in a better way than the FreeBSD 
> ports framework allows, like in a file /etc/mk.conf (pkgsrc) or USE= ... as 
> in /etc/make.conf (Gentoo portage).
>
> Dialog4ports is better than the previous dialog but not as good as seeing in 
> a file mk.conf or make.conf .
>
> Otherwise, I don't really know any elegant way to fix the options mess I got 
> into.

Any reason why don't you can't all your options into /etc/make.conf?
I've never used /var/db/ports options as they're not easy to review in
one go.

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: Synth and circular dependencies

[Don Lewis]

On 21 Aug, Thomas Mueller wrote:
> from RW rwmaillists at googlemail.com
> Mon Aug 21 15:28:49 UTC 2017:
> 
>> On Mon, 21 Aug 2017 13:19:24 +
>> Thomas Mueller wrote:
> 
> 
>> > But on this computer, no such system crashes, but I ran into
>> > circular dependencies
> 
>> Try removing any port options that aren't absolutely essential.
> 
>> > It seems the ports go overboard with an awful lot of dependencies,
>> > of which not all install with the main port.  So I expect some of
>> > these dependencies might be false dependencies.
> 
>> They are probably just build dependencies.
> 
> It is still disappointing to find devel/git or sysutils/coreutils were
> not installed.
> 
> Email from FreeBSD lists is slow coming to my inbox, so I am
> respoonding from the web interface to the emailing lists, and on the
> other computer, now running NetBSD.
> 
> I ran "make show-depends" on NetBSD with pkgsrc, dependencies are
> generally far less/fewer than on FreeBSD with ports.
> 
> But FreeBSD ports seems to go overboard now with dependencies,
> creating circular dependencies along the way.
> 
> I rebooted to an older FreeBSD installation (current/11 amd64 from
> January 2016, no longer supported).
> 
> I went to /usr/ports/textproc/xmlto , ran "make all-depends-list", and
> one line that showed up was
> /usr/ports/textproc/xmlto
> 
> depends on itself.

I don't see that here with default option settings:

%cd /usr/ports/textproc/xmlto && make all-depends-list | grep textproc
/usr/ports/textproc/libxml2
/usr/ports/textproc/libxslt
/usr/ports/textproc/docbook-xsl
/usr/ports/textproc/xmlcatmgr
/usr/ports/textproc/docbook
/usr/ports/textproc/docbook-sgml
/usr/ports/textproc/iso8879
/usr/ports/textproc/docbook-xml
/usr/ports/textproc/xmlcharent
/usr/ports/textproc/sdocbook-xml

> Otherwise, on newer system, I see circular dependencies running "make
> all-depends-list", finding textproc/xmlto depended on graphics/gd and
> vice versa.

I don't see the former:

%cd /usr/ports/textproc/xmlto && make all-depends-list | grep graphics
[nada]

or the latter:

%cd /usr/ports/graphics/gd && make all-depends-list | grep textproc 
/usr/ports/textproc/expat2

This is with the head branch of the ports tree, revision r448344.

Problems like this with the default option settings tend to get found
and fixed fairly quickly because this will cause failures on the package
build cluster and will spam the maintainer's mailbox with build failure
messages.


___
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: Synth and circular dependencies

[Thomas Mueller]

from RW rwmaillists at googlemail.com
Mon Aug 21 15:28:49 UTC 2017:

> On Mon, 21 Aug 2017 13:19:24 +
> Thomas Mueller wrote:


> > But on this computer, no such system crashes, but I ran into circular
> > dependencies 

> Try removing any port options that aren't absolutely essential.

> > It seems the ports go overboard with an awful lot of dependencies, of
> > which not all install with the main port.  So I expect some of these
> > dependencies might be false dependencies.

> They are probably just build dependencies.

It is still disappointing to find devel/git or sysutils/coreutils were not 
installed.

Email from FreeBSD lists is slow coming to my inbox, so I am respoonding from 
the web interface to the emailing lists, and on the other computer, now running 
NetBSD.

I ran "make show-depends" on NetBSD with pkgsrc, dependencies are generally far 
less/fewer than on FreeBSD with ports.

But FreeBSD ports seems to go overboard now with dependencies, creating 
circular dependencies along the way.

I rebooted to an older FreeBSD installation (current/11 amd64 from January 
2016, no longer supported).

I went to /usr/ports/textproc/xmlto , ran "make all-depends-list", and one line 
that showed up was
/usr/ports/textproc/xmlto

depends on itself.

Otherwise, on newer system, I see circular dependencies running "make 
all-depends-list", finding textproc/xmlto depended on graphics/gd and vice 
versa.

It didn't seem broken back in January 2016, and I still use it for Seamonkey 
2.39 and other things.


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: Synth and circular dependencies

[RW via freebsd-ports]

On Mon, 21 Aug 2017 13:19:24 +
Thomas Mueller wrote:


> But on this computer, no such system crashes, but I ran into circular
> dependencies 

Try removing any port options that aren't absolutely essential.

> It seems the ports go overboard with an awful lot of dependencies, of
> which not all install with the main port.  So I expect some of these
> dependencies might be false dependencies.

They are probably just build dependencies.
___
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"

Synth and circular dependencies

[Thomas Mueller]

I am on a FreeBSD 11.1-STABLE amd64 system, building ports with synth, started 
off really strong.

On the other computer (motherboard MSI Z77 MPOWER), synth doesn't work well, 
can't build packages, crashes the system most of the time.

But on this computer, no such system crashes, but I ran into circular 
dependencies which seemed related to print/texlive ports.

Synth screen output was, on several runs


graphics/gd scan aborted because a circular dependency on graphics/gd was 
detected.
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd

textproc/docproj scan aborted because a circular dependency on graphics/gd was 
detected.
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd
... backtrace graphics/scr2png
... backtrace textproc/docproj

math/gnumeric scan aborted because a circular dependency on print/texlive-texmf 
was detected.
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-formats
... backtrace print/tex-jadetex
... backtrace textproc/docbook-utils
... backtrace graphics/colord
... backtrace x11-toolkits/gtk30
... backtrace databases/libgda5-ui
... backtrace math/gnumeric

www/seamonkey-i18n scan aborted because a circular dependency on 
print/texlive-texmf was detected.
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-formats
... backtrace print/tex-jadetex
... backtrace textproc/docbook-utils
... backtrace graphics/colord
... backtrace x11-toolkits/gtk30
... backtrace www/seamonkey
... backtrace www/seamonkey-i18n


Only web browser I built successfully was elinks; SeaMonkey, Firefox, Otter 
browser and Netsurf all failed on similar circular dependencies.

I think the fault is in the print/texlive ports rather than synth, but I could 
be wrong.  Abiword also failed on similar circular dependency.

I was successful building llvm40, Xorg, IceWM, jwm, i3 and ratpoison (four 
window managers) but haven't run them yet.

It seems the ports go overboard with an awful lot of dependencies, of which not 
all install with the main port.  So I expect some of these dependencies might 
be false dependencies.

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"