Bug 202725 - [feature request] IMPLIES/PREVENTS support for ports-mgmt/dialog4ports
Summary: [feature request] IMPLIES/PREVENTS support for ports-mgmt/dialog4ports
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Adam Weinberger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-28 18:39 UTC by Adam Weinberger
Modified: 2018-05-18 16:04 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (rum1cro)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Weinberger freebsd_committer freebsd_triage 2015-08-28 18:39:55 UTC
OPTIONS_DEFINE=    FOO IMP1 IMP2 PRE1 PRE2
FOO_IMPLIES=       IMP1 IMP2
FOO_PREVENTS=      PRE1 PRE2

Can digalog4ports learn to parse the above and, when FOO is highlighted, say somewhere at the bottom:

"Enabling FOO will automatically enable IMP1 and IMP2"
"FOO cannot be used with PRE1 or PRE2"
Comment 1 ru_M1cRO 2015-08-29 14:45:15 UTC
Give me few days.
Comment 2 Adam Weinberger freebsd_committer freebsd_triage 2016-03-12 19:21:17 UTC
Any thoughts on this?
Comment 3 ru_M1cRO 2016-03-14 20:36:11 UTC
Sorry, I forget about this PR >_<
I will do it ASAP.
Comment 4 Walter Schwarzenfeld freebsd_triage 2018-01-13 06:12:55 UTC
Is this still relevant?
Comment 5 Adam Weinberger freebsd_committer freebsd_triage 2018-01-13 06:34:20 UTC
(In reply to w.schwarzenfeld from comment #4)
Yes.
Comment 6 ru_M1cRO 2018-01-24 14:57:18 UTC
damn.... i'll do it.
Comment 7 Adam Weinberger freebsd_committer freebsd_triage 2018-05-18 15:30:53 UTC
It's been almost 3 years since this bug was filed. There's no indication that people are struggling with the concept, so there's really no need for dialog4ports to change its behaviour.

Closing this as not needed.
Comment 8 ru_M1cRO 2018-05-18 15:59:59 UTC
sorry...
Comment 9 Adam Weinberger freebsd_committer freebsd_triage 2018-05-18 16:04:10 UTC
(In reply to m1cro from comment #8)
No worries. It wasn't worth you doing the backend work for it.