Subject: make release or build.sh -R and MKPROFILE=no ?
To: None <firstname.lastname@example.org>
From: Martin Weber <Ephaeton@gmx.net>
Date: 02/05/2002 15:08:50
Hoi, I recently noticed that when you set MKPROFILE=no in
your mk.conf the make release, be it invoked via make release
or build.sh -R fails due to lacking profiled libraries in
DESTDIR which could be packed up. I wonder now if this
behaviour is wanted (always make sane releases to keep
uniformity) or if you should be able to bake noprofile releases.
In either way: there's a problem.
If it's a wanted behaviour (which I'd understand) then that
needs to be documented in BUILDING, in the paragraph of MKPROFILE.
Something like "A release needs this variable unset." or unset it
automatically and document it, whatever...
If it's supposed to be working to bake noprofile releases, then
that's broken :)