Date: Thu, 17 Mar 2022 04:08:58 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262609] ports-mgmt/poudriere "options" mode doesn't correctly assess -C (only present changed options dialogue) Message-ID: <bug-262609-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262609 Bug ID: 262609 Summary: ports-mgmt/poudriere "options" mode doesn't correctly assess -C (only present changed options dialogue) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: bdrewery@FreeBSD.org Reporter: dgilbert@eicat.ca Flags: maintainer-feedback?(bdrewery@FreeBSD.org) Assignee: bdrewery@FreeBSD.org The easiest way to look at this bug is to examine the behavior... and to do that, we need an example. For my example, I'll use the kicad ports --- the= re's half a dozen of them or so. Obviously, I noticed things because the kicad ports all have similar sets of dependencies. With options -C, I'd expect to set each dependant port's opt= ions once. When I invoke poudriere options -p HEAD -C -f my-list-of-ports, howev= er, I end up cycling through the same bunch of ports for each kicad port. It prints out "Options unchanged." each time ... even though I'm setting an op= tion in some of those ports (TEST, in a few cases) ... each time it comes back to that port, the option is unset again (making it frustrating if I miss setti= ng the option the last time it comes around). Even after running a successful round of poudriere options, and without updating ports, running it again with the same list of ports brings up opti= ons dialogues. ... now this also might be something with the ports machinery itself, but I staked the PR here because I didn't know where else to put it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262609-7788>