From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D077915800F for ; Fri, 6 Jan 2023 18:53:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5DE7BE0867; Fri, 6 Jan 2023 18:53:06 +0000 (UTC) Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 32512E0863 for ; Fri, 6 Jan 2023 18:53:06 +0000 (UTC) Received: by mail-qk1-x736.google.com with SMTP id pe2so1165170qkn.1 for ; Fri, 06 Jan 2023 10:53:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=fWqmQdWDYc+bLKbBX3fFtOaMSTiCO7gA24XTuMu9uSc=; b=DU1XGG/NPfr1vWZ77h9kOj6sWufxytl6YB3ZSWYdgwzfdTn8jPOSUN6Q7areeLfVHE 5PY6pBksEr6R3ZNJmHEbmTxh8k/Ve/Lo9H+Oe2Yxp9XtBy6n4FFgUodfsFsLM9Es3/BG uNw8AtSJYuPeV4csDQqwTwiULjPrPbXL/v9U6NzO9+xM27k4uSPuUzxC7SWS37sh0Q2F /c0ZjdkZR5Z9p79M+uWYU6UP6UwzQqQfoe0F/mWMwslYh1RedpW+JWw4cjRH/WgyvkXe sExoeVq8CYsYjZkBldGXt/3BO17d4oDAtLgGiCcDPPjhNhCFQG9UgRwBt1ckLdzjUEjo nVVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fWqmQdWDYc+bLKbBX3fFtOaMSTiCO7gA24XTuMu9uSc=; b=TfBcZsvkJ6KywSrUyz1u26MN3RABQSd5HXPWVd97OESEO0/GO5oI6qv3/i5dBB3tqo pF4558Nbuy2p9bEdiZQSnikZrFMCHMXfQYLC1L6comj40kJXofAcvmHO5N7uWO6WXoUi U28VM6c1zv9GLP/wKlffJSg3SK7mDbyJYZk44VjCimWVezSY9aiWWeSd3fHUsqmwR+gE vhJP7no7fGEP4eMgf9EzTm6m0jvelW86fZkI2NfpaW61K2HSLJ2Mg+MNSeU3KnJWvlDa K8pCIsLbZVmvj8CpO+yfvR6F29pFZ+C0UWqVW8uJB0ypahUhVamQqXNWO4Au5+sMXs2S +GjQ== X-Gm-Message-State: AFqh2krugBO3/0+0CIbJGeuNLvMhDy40/ZUelmk7CQON/dxamkw6swVF Jhp4TVfCQpy0E7OFaKQwh/cFltwPfNIZK7H0MS04BkJgNsKdaQ== X-Google-Smtp-Source: AMrXdXtKMXSVRlU4LqZjpUxdt+xv1rERDv3hYG7Nxh5n4oj1ATPVkK50MM0MB20MvlWnWMppJ8Ing8VVdVC9aiP7cYc= X-Received: by 2002:a05:620a:1d92:b0:6fe:e6c3:2d3e with SMTP id pj18-20020a05620a1d9200b006fee6c32d3emr2980664qkn.365.1673031185039; Fri, 06 Jan 2023 10:53:05 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20230106172051.274199-1-flow@gentoo.org> In-Reply-To: <20230106172051.274199-1-flow@gentoo.org> From: "Yuan Liao (Leo)" Date: Fri, 6 Jan 2023 10:52:00 -0800 Message-ID: Subject: Re: [gentoo-dev] RFC: new gradle.eclass To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 9c424370-e6e8-43a5-a31f-8703276a2ed5 X-Archives-Hash: 08e3bf5414b14d96840e2ef5fca30436 While I warmly appreciate and welcome any effort to improve support for Java build systems on Gentoo, I also wonder what functionality ebuild authors who are creating a Java package might expect from an eclass called "gradle.eclass". I'm not doubting this eclass's usefulness -- to me, it looks like a convenient eclass when a Gradle project's dependencies are vendored and included in SRC_URI. Specialized eclasses are totally fine as we've already got plenty of them in the tree. But I think what an average Java ebuild author often wants is an eclass with which they can just declare all dependencies of the Gradle project in *DEPEND variables, and rely on the default pkg_* and src_* functions from the eclass to do the rest, with no or only minimal overrides necessary. They might trust the eclass to introduce any Java dependencies installed by Portage to Gradle, invoke the build system, and finally install the JARs built. Maybe we will be lucky enough to have such an eclass in the future. But should we add a remark to the eclass's description to warn that this might not be the generalized "gradle.eclass" suitable for packaging most Gradle-based projects, if that is what people would believe a "gradle.eclass" would do for them? Leo3418 On Fri, Jan 6, 2023 at 9:21 AM Florian Schmaus wrote: > > Happy new year everyone! > > I'd like to as for a review of an initial eclass for gradle. This is my > first eclass, so I am sure there is plenty to find. ;) > > The related github PR is https://github.com/gentoo/gentoo/pull/28986 > > - Flow > >