From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hartmut Goebel Subject: Re: maven build system - new insights Date: Tue, 5 Feb 2019 13:00:45 +0100 Message-ID: References: <71F627FD-4E2E-4E8D-B73E-433368CE3B6B@lepiller.eu> <87ef8smmgj.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59878) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqzaZ-0005U5-5Z for guix-devel@gnu.org; Tue, 05 Feb 2019 07:12:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gqzPI-0008Ew-6u for guix-devel@gnu.org; Tue, 05 Feb 2019 07:00:53 -0500 Received: from mail-out.m-online.net ([2001:a60:0:28:0:1:25:1]:53294) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gqzPH-00088v-V8 for guix-devel@gnu.org; Tue, 05 Feb 2019 07:00:52 -0500 In-Reply-To: <87ef8smmgj.fsf@elephly.net> Content-Language: en-US List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel Am 01.02.19 um 00:33 schrieb Ricardo Wurmus: > Hartmut Goebel writes: >> The drawback of this approach is: This only works within the >> build-system. Since within a normal environment or profile, there will= >> be no such unison repo. Thus for every day's work, users will still >> download artifacts from the Internet and will not be able to use those= >> already installed on the system. > A profile *is* a union of all installed packages. If that=E2=80=99s no= t enough > and more configuration is required we could do that in a profile hook. I didn't know about the profile hooks. Nevertheless: I want to emphasis that maven does *not* support some kind of "system repository", as I explained in my original post. Even if you mimic a "system repository", this will always *copy* the artifacts to $HOME/.m2/repository. Debian uses some *extensions* to make maven use some "system repository" - at least this is what I assume. So this is much like xmvn, with a difference that end-users can not use it easily. Beside this: I suggest first of all to design the expected behavior, that reach out for a solution. Who is the one driving this? (I'm not, I can't program guile :-) --=20 Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |