Re: [kde-freebsd] XDG_* make environment variables
Schaich Alonso alonsoscha...@fastmail.fm writes:
Hello
About a year ago several area51 ports introduced an explicit XDG_CONFIG_HOME
and/or XDG_DATA_DIRS assignment to /dev/null, iirc in order to prevent the
build process to create paths in the home directory of the building user.
Earlier today I was browsing some ${PORTSDIR}/Mk/... files and noticed
Mk/bsd.port.mk sets both variables to WRKDIR. The way I see this, it
should therefore be safe to remove the explicit value overloads in the
area51 ports, but I haven't tried doing so yet.
Is there anything that still needs them?
This was mostly done by avilla and bapt back in the days because
update-mime-database or something else that touched $HOME was being
called during the build or installation.
I'd say if svn blaming the changes to bsd.port.mk shows they're more
recent than those changes to XDG_* variables in the Makefiles (and your
tests still work), then we can go ahead.
bapt, do you have anything to add here?
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] XDG_* make environment variables
On Fri, Sep 05, 2014 at 07:41:33AM -0300, Raphael Kubo da Costa wrote:
Schaich Alonso alonsoscha...@fastmail.fm writes:
Hello
About a year ago several area51 ports introduced an explicit XDG_CONFIG_HOME
and/or XDG_DATA_DIRS assignment to /dev/null, iirc in order to prevent the
build process to create paths in the home directory of the building user.
Earlier today I was browsing some ${PORTSDIR}/Mk/... files and noticed
Mk/bsd.port.mk sets both variables to WRKDIR. The way I see this, it
should therefore be safe to remove the explicit value overloads in the
area51 ports, but I haven't tried doing so yet.
Is there anything that still needs them?
This was mostly done by avilla and bapt back in the days because
update-mime-database or something else that touched $HOME was being
called during the build or installation.
I'd say if svn blaming the changes to bsd.port.mk shows they're more
recent than those changes to XDG_* variables in the Makefiles (and your
tests still work), then we can go ahead.
bapt, do you have anything to add here?
In theory you do not need anymore FreeBSD specify hacks as the bsd.port.mk does
all it needs.
A good way to test it to run poudriere testport or bulk -t it will show you fs
violation if the problem remains.
regards,
Bapt
pgpYQHPzoRiZZ.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
[kde-freebsd] [Bug 193336] Error Compile port of textproc/qt4-xmlpatterns on FreeBSD 10.0-RELEASE amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193336 Mark Linimon lini...@freebsd.org changed: What|Removed |Added Assignee|freebsd-ports-bugs@FreeBSD. |k...@freebsd.org |org | -- You are receiving this mail because: You are the assignee for the bug. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
