Received: from cogitri.dev (cogitri.dev [207.180.226.74]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id CFC5D782BA9 for <~alpine/devel@lists.alpinelinux.org>; Thu, 21 May 2020 14:56:34 +0000 (UTC) X-Virus-Scanned: Yes Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1590072992; bh=i2tEEH+KUNd3MyDSZHk5ifxqhFNURz4x1+qNIwtWhXI=; h=Subject:From:To:In-Reply-To:References; b=x1+9U/sUh6D0pc5NOCtkcsz6Y8yNLglFZOSdk0BHAzKtvdh+RCsZP34U/PKBK68E1 8KFx/VrAwdXneUt9Pl6T7VaeD5L37bNIaWU+awktustAyYi0Tegqwz2Y3PRLMREFIO 0/V6PmGw0nKyKV1LUij4zQzN9Tsp1hC+GK2hKe4uXYc7U9WJtOm2py5+/Pu4h7dsmL fEvgWx2w+VT0EibbHniO4yOEHwzKY+e/pnaA7bzGiqxZJti1FCqaidEQcJd4QWIJbi X+A/vJl0MFyYHSryHNo0AEca6YFSfPjIm0ABOc8lu/4KJ32Ci4DlZaKt6FKECCgI4W aBexO8gbc3CUg== Subject: Re: RFC: tool to scan aports tree From: Rasmus Thomsen To: Natanael Copa , Alpine develmopment <~alpine/devel@lists.alpinelinux.org> Date: Thu, 21 May 2020 16:56:31 +0200 In-Reply-To: <20200521154157.6df2d118@ncopa-desktop.copa.dup.pw> References: <20200521154157.6df2d118@ncopa-desktop.copa.dup.pw> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit On Thu, 2020-05-21 at 15:41 +0200, Natanael Copa wrote: > I would like to have some feedback on how you would like that the > interface should be? One thing I'd really love that tool to have would be more usability for developers, see below. > I am not sure those are needed: > > [...] > - print the reverse build time dependencies for a given package (ap > revdep) That one might be useful for developers to rebuild things on soname bumps. Right now it's kind of a pain to rebuild everything in the right order when soname bumps occur, it'd be lovely if the new tool had something git-bisect-ish. That is if I could tell it "package X changed, run script Y for all packages that (directly) depend on it". > Things that the tools needs to be able to help us to do: > > - detect if there are any invalid dependencies (eg. packages in main > that depends on packages in community or testing) I think that is something that CI catches anyway these days - but it might be useful when demoting a packge from main to community (or community -> testing). > - detect missing build time dependencies (due to arch being disabled) That sounds a bit redundant, you'd notice that when running abuild. > - detect circular build time dependencies That would be something that'd be really nice to have for CI so we don't run into these in the first place. > - clean source cache (delete downloaded sources older than X that is > not currently used by any aports) That sounds nice, I usually do `rm -rf */*/src` in my aports tree every month or so when my disk starts filling up once again. It'd be nice if this could be run automatically somehow so I..err users don't forget to run this before things start to blow up because there's no space left in / once again ;) > - implement relgroups (check that all aports with same relgroup has > same pkgver - this is not in use in aports yet) Ah, that'd for things like sqlite-tcl and sqlite to make sure they're the same version? That'd be very nice to have for CI. > - print reverse build deps. If you for example disable/enable a > library > for an architecture, what other packages needs also to be > disabled/enabled. I think it'd be nice if this also had the ability to run a script for each affected package. Maybe functionality that enables/disables the affected packages on all arches the affected package is disabled on would be good to have too (and very helpful when bootstrapping new arches), or when enabling core packages on a certain arch (e.g. when Rust was made available for more arches). Thanks for working on this, Rasmus