From: Andrew Cagney <cagney@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: enabling shared builds
Date: Thu, 13 Dec 2007 23:19:00 -0000 [thread overview]
Message-ID: <4761BDEA.6040804@redhat.com> (raw)
In-Reply-To: <20071213213703.GA2300@oracle.com>
Kris Van Hees wrote:
>> Andrew Cagney wrote:
>> - switch to install-tree testing
>> Would mean breaking configure convention and set --prefix=. On the other
>> hand it would mean only testing one way.
>>
>
>
Seems I've created a little confusion with "and set -prefix". I don't
think anyone was thinking of installing into /usr, which, if nothing
else, would require root privileges.. --prefix would need to be pointed
at something like $BUILD/_oinst and then overridden when doing a system
build/install.
Andrew
> Definitely a big 'no' on this one. For one, forcing an install of development
> builds in order to be able to test it is asking for trouble. Secondly, it is
> (hopefully) going to be more likely in the future that a system will have frysk
> already installed as part of the OS install, and a development build shouldn't
> wipe out the installed version for sure. Thirdly, it is common practice with
> software projects to follow a 'build -> test -> install' sequence, which is
> generally the most sensible way because you wouldn't want to install something
> that is broken, i.e. test before you install.
>
> Cheers,
> Kris
>
next prev parent reply other threads:[~2007-12-13 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 14:50 Andrew Cagney
2007-12-13 15:02 ` Phil Muldoon
2007-12-13 21:38 ` Kris Van Hees
2007-12-13 23:19 ` Andrew Cagney [this message]
2007-12-13 23:58 ` Kris Van Hees
2007-12-13 16:13 ` Petr Machata
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4761BDEA.6040804@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sources.redhat.com \
--cc=kris.van.hees@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).