-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for CONFLICTS #84
Comments
I really like this idea. My first reading is that CONFLICTS contains the PKG_NAME value, which is already stored in the database. Should be very straight forward to do this. I think it's a great idea. |
Plot twist: CONFLICTS variables can contain wildcards and regexy-type things. Example: |
From https://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?view=markup#l436
See also https://www.freebsd.org/doc/en/books/porters-handbook/conflicts.html |
Your task: find out if the field contains a regex or not. Using php. |
These three new columns with each contain their respective values obtained directly from the Makefile via:
For example:
Column creation:
|
Linking to the discussions on the mailing lists: https://lists.freebsd.org/pipermail/freebsd-ports/2018-August/114084.html |
I see conflicts listed at https://www.freshports.org/sysutils/bacula9-server/ See also #103 |
This comment was marked as resolved.
This comment was marked as resolved.
Done. Example: https://dev.freshports.org/sysutils/bacula13-server/#conflicts and I added a tag for it. I also added in a new tag: https://dev.freshports.org/sysutils/bacula13-server/#pkg-plist |
It would be neat to see the conflicts for ports and be able to follow links to ports that match the expression.
You would want to support parsing:
CONFLICTS, CONFLICTS_INSTALL and CONFLICTS_BUILD
The text was updated successfully, but these errors were encountered: