From mint-bounce@lists.fishpool.fi Mon Oct 13 10:24:45 2008 Message-ID: <48F35852.8070209@atari-source.org> Date: Mon, 13 Oct 2008 10:16:50 -0400 From: Mark Duckworth User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: Miro Kropacek CC: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= , mint@lists.fishpool.fi Subject: Re: [MiNT] distro cross-building References: <200810110019.01757.oak@helsinkinet.fi> <48EFD0D0.3040707@atari-source.org> <200810112257.48424.oak@helsinkinet.fi> <48F1B5F6.20607@freesbee.fr> <48F2C5E3.6050900@atari-source.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Miro Kropacek wrote: > > How would you indicate that dependent packages need updated... > i.e. we statically link everything to mintlib, mintlib is updated, > every package would then need to be updated to reflect this > change... how would we handle this elegantly? > > Don't know if it's elegant but the idea was to make nightly builds for > every package so this shouldn't be much different. We have maybe 100 > packages so this is task maybe for 2-3 hours with cross compiler, right? > Yes but then users can't be expected to download all 100 packages every night because some might possibly have been rebuilt? Dynamic linking was designed as the best solution to this problem so it seems reasonable that that's what we should aim for ;) Thanks, Mark