All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@XenSource.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Alex Williamson <alex.williamson@hp.com>
Subject: RE: Re: [Xen-staging] [xen-unstable] If we find aLinuxrepository in $(LINUX_SRC_PATH) then symlink it
Date: Tue, 05 Jun 2007 16:27:36 +0100	[thread overview]
Message-ID: <1181057256.4041.91.camel@localhost.localdomain> (raw)
In-Reply-To: <FE7BBCFBB500984A9A7922EBC95F516E32C7C9@pdsmsx414.ccr.corp.intel.com>

On Tue, 2007-06-05 at 16:29 +0800, Cui, Dexuan wrote:
> In my host, "hg path default" points to an internal host(http://staging-mirror:8000) that mirrors http://xenbits2.xensource.com/staging/xen-unstable.hg.
> So I should mirror http://xenbits2.xensource.com/staging/linux-2.6.18-xen.hg also? What should I set the default hg path to?

I think this setup is going to break the scheme which we have.

We derive the Linux path from 
	$(dirname $(hg path default))/linux-2.6.18-xen.hg
which is going to be http://linux-2.6.18-xen.hg for you which is
completely wrong. Presumably you need
http://staging-mirror:<some-other-port> which unfortunately cannot be
automatically derived.

I can suggest a few workarounds, if you have any other ideas I'd be glad
to consider them.

You could set XEN_LINUX_HGREPO in your environment to point to the
correct mirror.

Alternatively you could pre-clone linux-2.6.18.hg into your source tree,
then the build will simply use it. Or you could pre-clone
linux-2.6.18.hg in the same directory as your xen-unstable.hg and the
build system will then use that, via $(LINUX_SRC_PATH) which is ".:.."
by default.

We could check in select-repository for "hg path default-linux" before
we go down the route of deriving the path from "hg path default". Then
you could add the correct path to .hg/hgrc. If this seems acceptable let
me know (preferably with a patch ;-))

> Btw: it seems "make world" first deletes the directory
> "xen-top-level-dir/ linux-2.6.18-xen.hg" if the directory exists --
> this means I have to clone the linux-2.6.18-xen.hg every time I make
> world?

make world is the same as "make clean kdelete dist", so yes it will
delete the repositories, in the same way it used to delete linux-FOO,
ref-linux-FOO and pristine-linux-FOO requiring you to unpack and repatch
again.

Ian.

  reply	other threads:[~2007-06-05 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200706041442.l54EgKQp007662@latara.uk.xensource.com>
2007-06-04 18:49 ` [Xen-staging] [xen-unstable] If we find a Linux repository in $(LINUX_SRC_PATH) then symlink it Alex Williamson
2007-06-04 21:37   ` Ian Campbell
2007-06-04 21:44     ` Alex Williamson
2007-06-04 22:03       ` Ian Campbell
2007-06-04 22:19         ` Alex Williamson
2007-06-05  7:11           ` Ian Campbell
2007-06-05  7:31             ` Re: [Xen-staging] [xen-unstable] If we find a Linuxrepository " Cui, Dexuan
2007-06-05  7:54               ` Ian Campbell
2007-06-05  8:29                 ` Re: [Xen-staging] [xen-unstable] If we find aLinuxrepository " Cui, Dexuan
2007-06-05 15:27                   ` Ian Campbell [this message]
2007-06-05  7:59             ` Re: [Xen-staging] [xen-unstable] If we find a Linux repository " Ian Campbell
2007-06-05 14:21               ` Alex Williamson

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=1181057256.4041.91.camel@localhost.localdomain \
    --to=ian.campbell@xensource.com \
    --cc=alex.williamson@hp.com \
    --cc=dexuan.cui@intel.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.