From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: 3.4.0 wants to download Linux despite its presence Date: Wed, 20 May 2009 14:12:00 -0700 Message-ID: <4A147220.9010503@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Ian Jackson List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 20/05/2009 07:57, "Ian Jackson" wrote: > > >>> Much better would be to just list what the dependencies are in the >>> README, as well as where to get them. If the build finds them missing, >>> then it should just say so and stop. >>> >> I would actually agree. Having a part of the build system which >> brings all the pieces together automatically for you would be good, >> but it would be sensible for xen-unstable.hg to be less enthusiastic >> about downloading stuff. >> > > Perhaps we should more prominently advertise 'make install-xen > install-tools'. This should generally result in no downloads apart from > qemu, and that's a special-case dependency since it ties quite closely to > xen-unstable -- we can't just use any qemu tree. And of course you can > define XEN_EXTFILES_URL so as to make any download attempt fail, and then > you can go grab the packages yourself as you see fit and assemble your > requirements list. Imagine the noise on the mailing list if xen-unstable > didn't try to assemble itself automatically out of the box. > What about adding "make fetch-dependencies", and have the default build say something like "X is missing. Type "make fetch-dependencies"."? J