public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
	frysk <frysk@sources.redhat.com>
Subject: Re: enabling shared builds
Date: Thu, 13 Dec 2007 23:58:00 -0000	[thread overview]
Message-ID: <20071213235546.GB2300@oracle.com> (raw)
In-Reply-To: <4761BDEA.6040804@redhat.com>

On Thu, Dec 13, 2007 at 06:19:06PM -0500, Andrew Cagney wrote:
> 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.

That does indeed resolve the issue of overwriting an existing installation
but it does nothing to avoid the fundamental problem with requiring to do
the install step prior to running development tests.  This is exactly the
kind of situation where software engineering commonly separates the
development testsuite from a release testsuite (which is typically done
on an installed version of the project).

I am sure someone can come up with an existing project that does require
installation in some location prior to running development level tests, but
I honestly cannot remember ever encountering a single one.  We're facing a
quite common problem, so I think we ought to be able to pick an already well
established solution, and run with it.

	Cheers,
	Kris

  reply	other threads:[~2007-12-13 23:58 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
2007-12-13 23:58       ` Kris Van Hees [this message]
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=20071213235546.GB2300@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=cagney@redhat.com \
    --cc=frysk@sources.redhat.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).