Skip to content

Conversation

darkain
Copy link

@darkain darkain commented Aug 1, 2025

More details can be found on Bugzilla:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268630#c17

@lwhsu
Copy link
Member

lwhsu commented Aug 1, 2025

Please note that the PORTREVISION needs to be bumped here.

@darkain
Copy link
Author

darkain commented Aug 1, 2025

PORTREVISION changes would get into murky territory because this port is a child-port of another port. Would we carry that indefinitely, or would changes to the parent-port be cognitive to this PORTREVISION and reset it when updating there? Also generally speaking, this isn't even a normal "installable" port, it is part of the build process of generating FreeBSD SD card image files.

@bsdimp
Copy link
Member

bsdimp commented Aug 1, 2025

I'd be tempted to just do a PORTREVISION in the parent port. That would go away with the next update.

@arrowd
Copy link
Contributor

arrowd commented Aug 15, 2025

The common solution for this is that master ports should always have PORTREVISION variable, like

PORTREVISION?= 0

This allows for slave ports to have their own revisions independent of master.

@diizzyy
Copy link
Contributor

diizzyy commented Aug 16, 2025

This still needs to go via bugzilla to land

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants