Page MenuHomeFreeBSD

Mk/bsd.port.mk: Be verbose when pkgconfig files ends up in wrong path
AbandonedPublic

Authored by diizzy on Jan 20 2023, 2:10 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 10 2024, 7:13 PM
Unknown Object (File)
Feb 1 2024, 12:06 PM
Unknown Object (File)
Jan 18 2024, 1:42 PM
Unknown Object (File)
Jan 13 2024, 8:23 AM
Unknown Object (File)
Dec 24 2023, 8:25 PM
Unknown Object (File)
Dec 23 2023, 1:46 AM
Unknown Object (File)
Nov 27 2023, 9:57 AM
Unknown Object (File)
Nov 11 2023, 1:12 PM

Details

Reviewers
None
Group Reviewers
portmgr
Summary

While this is applied for convenience we shouldn't silently hide fixups

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

diizzy created this revision.
tcberner added inline comments.
Mk/bsd.port.mk
3542

I wonder whether it would make more sense to add it to DEV_WARNINGS and not to echo it manually.

mat added inline comments.
Mk/bsd.port.mk
3542

DEV_WARNINGS and WARNINGS are like, static things, that run before everything, they can't really know what will happen during staging.

Mk/bsd.port.mk
3542

hm, then maybe manually check for the DEVELOPER mode?
I doubt there is much benefit in non-maintainers reading the message.

Mk/bsd.port.mk
3542

I think it can be useful in general as this "silent fix" causes a different end result than what build log shows.

Should this go in or is it deemed unnecessary?

I can't seem to edit and propose a change for some reason, but, change it to something like this:

                    if [ -n "${DEVELOPER:Dyes}" ]; then \
			${ECHO_MSG} "===>   File(s) found in lib/pkgconfig while correct path is libdata/pkgconfig"; \
			${ECHO_MSG} "       Applying fix but consider using USES= pathfix or adjust install path"; \
                    fi; \

Only display message when DEVELOPER variable is set as suggested by mat