Andrew Cooper writes ("Re: [PATCH XTF] Correct the usage of $(DESTDIR) and
$(prefix)"):
> XTF doesn't match any standard installable package. It is some
> configuration files and a load of microkernels which are not system
> executables.
The question is what
really make install prefix=/usr
sho
On 21/07/16 11:43, Ian Jackson wrote:
> Andrew Cooper writes ("[PATCH XTF] Correct the usage of $(DESTDIR) and
> $(prefix)"):
>> The GNU coding standards expect $(DESTDIR) to be the root of everything
>> installed, and for prefix to then be added to the path. This is not how XTF
>> previously beh
Andrew Cooper writes ("[PATCH XTF] Correct the usage of $(DESTDIR) and
$(prefix)"):
> The GNU coding standards expect $(DESTDIR) to be the root of everything
> installed, and for prefix to then be added to the path. This is not how XTF
> previously behaved.
>
> Replace $(PREFIX) with its more co
On Wed, Jul 20, 2016 at 07:21:46PM +0100, Andrew Cooper wrote:
> The GNU coding standards expect $(DESTDIR) to be the root of everything
> installed, and for prefix to then be added to the path. This is not how XTF
> previously behaved.
>
> Replace $(PREFIX) with its more common form $(prefix), a
On 7/20/16 1:21 PM, Andrew Cooper wrote:
> The GNU coding standards expect $(DESTDIR) to be the root of everything
> installed, and for prefix to then be added to the path. This is not how XTF
> previously behaved.
>
> Replace $(PREFIX) with its more common form $(prefix), and rearange $(DESTDIR)
The GNU coding standards expect $(DESTDIR) to be the root of everything
installed, and for prefix to then be added to the path. This is not how XTF
previously behaved.
Replace $(PREFIX) with its more common form $(prefix), and rearange $(DESTDIR)
and $(prefix) to match expectation.
Reported-by:W
