From owner-freebsd-ports Sat Nov 7 17:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10240 for freebsd-ports-outgoing; Sat, 7 Nov 1998 17:56:30 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10235 for ; Sat, 7 Nov 1998 17:56:29 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with ESMTP id TAA14782 for ; Sat, 7 Nov 1998 19:56:15 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 7 Nov 1998 19:56:15 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: freebsd-ports@FreeBSD.ORG Subject: Way to fetch distfiles for all dependancies? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I make up FreeBSD snapshot cdroms every once in a while, and one of the things I have done is create a script which goes into each directory of a list of ports i consider commonly-used (I can't fit _everything_ on the CD after all) and do a simple 'make fetch'. The only problem is, the distfiles for everything the port depends on aren't fetched, and I have to add those to my list also. If a dependancy isn't fetched, whoever I give the snapshot has to download it themselves. As quicky as things are being added/changed in the ports tree these days (thats GOOD!), it makes it a pain to maintain the list of a couple hundred ports and their dependancies. I've tried making a 'fetch-all' target in bsd.port*.mk without much luck. I don't understand all the intricacies of make and those .mk files, which are pretty complex. 'depends-list' doesn't give a port dir, just package name, so I can't easily grok that with a script of some kind to fetch what it lists. I've even tried a 'make all' with NO_BUILD, NO_INSTALL, NO_EXTRACT, and NO_WRKDIR defined, but that causes the patch process to fail. NO_PATCH is obsoleted, so that didn't help much, and I don't know if the end result would have been what I wanted anyway. Is there some functionality already existant that I'm missing that can do this? If not, how hard would it be to add a target which fetches everything a port depends on? Surely I'm not the only one that could benefit from this. I tried adding it myself, I really did, but I'm just make(1)-inept. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) ( http://www.freebsd.org ) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message