Bugzilla Automation has asked freebsd-xfce (Nobody)
for maintainer-feedback:
Bug 275487: x11-themes/xfce-icons-elementary (still) not prefix-safe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Description ---
Although the port's post-patch target attempts to fix PREFIX, it does t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
Bug ID: 275487
Summary: x11-themes/xfce-icons-elementary (still) not
prefix-safe
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
Guido Falsi changed:
What|Removed |Added
Flags|maintainer-feedback?(xfce@F |maintainer-feedback+
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
Guido Falsi changed:
What|Removed |Added
Attachment #246728|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Comment #3 from Mikhail T. ---
> The PREFIX variable is already included by default in MAKE_ENV
Maybe, that's only true during some stages :( Without the PREFIX added
explicitly, all of the files (except license) are installed under
wo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Comment #4 from Guido Falsi ---
(In reply to Mikhail T. from comment #3)
Thanks for the quick test.
Looks like the upstream Makefile has some issue though. I want to investigate a
little more. I'll followup as soon as I have some info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Comment #5 from Mikhail T. ---
(In reply to Guido Falsi from comment #2)
> The PREFIX variable is already included by default in MAKE_ENV
Being part of the /environment/ is unsufficient to overwrite the assignment
inside Makefile. My p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
Guido Falsi changed:
What|Removed |Added
Attachment #246730|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Comment #7 from Mikhail T. ---
Yes, the explicit setting of CONFIGURE_ARGS works just as well as that of
MAKE_ARGS. Why is one better than the other, I do not know, but I don't have to
know -- I'm not the port's maintainer :)
> But I f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Comment #8 from Guido Falsi ---
(In reply to Mikhail T. from comment #7)
> Why is one better than the other (?)
first of all we are running configure anyway so let's give it the correct
argument. Also, this is clearly how upstream int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=40eb0c4f9753d898422c4aa8d7882710be966f13
commit 40eb0c4f9753d898422c4aa8d7882710be966f13
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275487
Guido Falsi changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
13 matches
Mail list logo