From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 08575C433E0 for ; Mon, 3 Aug 2020 14:53:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D888E2076C for ; Mon, 3 Aug 2020 14:53:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726568AbgHCOxM (ORCPT ); Mon, 3 Aug 2020 10:53:12 -0400 Received: from raptor.unsafe.ru ([5.9.43.93]:57456 "EHLO raptor.unsafe.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726497AbgHCOxM (ORCPT ); Mon, 3 Aug 2020 10:53:12 -0400 Received: from comp-core-i7-2640m-0182e6 (ip-89-102-33-211.net.upcbroadband.cz [89.102.33.211]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by raptor.unsafe.ru (Postfix) with ESMTPSA id 20922209B2; Mon, 3 Aug 2020 14:53:10 +0000 (UTC) Date: Mon, 3 Aug 2020 16:53:08 +0200 From: Alexey Gladkov To: Luc Van Oostenryck Cc: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= / sparse , linux-sparse@vger.kernel.org Subject: Re: sparse | upgrade to upstream v0.6.2 (!2) Message-ID: <20200803145308.o2y4mln5fzlgdr4v@comp-core-i7-2640m-0182e6> References: <20200802213035.w7bexg4zdusr25xf@ltop.local> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200802213035.w7bexg4zdusr25xf@ltop.local> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.1 (raptor.unsafe.ru [5.9.43.93]); Mon, 03 Aug 2020 14:53:10 +0000 (UTC) Sender: linux-sparse-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-sparse@vger.kernel.org On Sun, Aug 02, 2020 at 11:30:35PM +0200, Luc Van Oostenryck wrote: > On Sun, Aug 02, 2020 at 08:18:42PM +0000, Uwe Kleine-König wrote: > > Uwe Kleine-König commented on a discussion: https://salsa.debian.org/ukleinek/sparse/-/merge_requests/2#note_185155 > > > > There is still another issue that popped up in the meantime: > > https://bugs.debian.org/966706 > > Hmmm, I think that a corner of my mind was silently worried it > will happen. > > > The options are: > > > > - add a Conflicts: biosquid > > (this is the ugliest option) > > - rename sindex to something else > > - convince the bioquid people to rename their sindex > > - stop shipping sindex > > > > For now I will go for "stop shipping sindex", do you have an opinion for a long-term plan? > > [+CC to sindex's author] > > Not really. > Would it be easy to install it under the name 'sparse-sindex' or > 'sparse-index'? > > One thing I would like (in some future release) is to split > the sparse package at least in 2: > * one with sparse itself > - it has no dependencies (except the libc, a compiler compatible > with gcc and GNU make for the build) > - maybe cgcc should be included in the package too (which would > add a dependency on perl) > * one with the others tools > - but maybe it would even be better to the big ones in their > own packages with their own dependencies) > But this would not really solve the problem here. Renaming of sindex was an option for me, but since you have a plan to split the package anyway, then I think it's better to do so. I tried to use the libsparse.a and it looks like it works fine [1]. I spoke with Oleg Nesterov and he also does not mind moving this utility to a separate repository. [1] https://github.com/legionus/sindex -- Rgrds, legion