linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: "Uwe Kleine-König / sparse"
	<gitlab+9b7df497d06cab14c2bf3c1022d8ca15@salsa.debian.org>
Cc: linux-sparse@vger.kernel.org, Alexey Gladkov <gladkov.alexey@gmail.com>
Subject: Re: sparse | upgrade to upstream v0.6.2 (!2)
Date: Sun, 2 Aug 2020 23:30:35 +0200	[thread overview]
Message-ID: <20200802213035.w7bexg4zdusr25xf@ltop.local> (raw)
In-Reply-To: <note_185155@salsa.debian.org>

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.

-- Luc

  parent reply	other threads:[~2020-08-02 21:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <reply-7f2b156a8ad4ece3334e6b9712c2de05@salsa.debian.org>
     [not found] ` <merge_request_28506@salsa.debian.org>
     [not found]   ` <note_184887@salsa.debian.org>
2020-08-01 16:54     ` sparse | upgrade to upstream v0.6.2 (!2) Luc Van Oostenryck
     [not found]   ` <note_184882@salsa.debian.org>
2020-08-02 13:29     ` Luc Van Oostenryck
2020-08-09 19:21     ` Luc Van Oostenryck
     [not found]   ` <note_185118@salsa.debian.org>
     [not found]     ` <note_185156@salsa.debian.org>
2020-08-02 21:09       ` Luc Van Oostenryck
     [not found]   ` <note_185002@salsa.debian.org>
     [not found]     ` <note_185155@salsa.debian.org>
2020-08-02 21:30       ` Luc Van Oostenryck [this message]
2020-08-03 14:53         ` Alexey Gladkov
2020-08-04 16:38           ` Alexey Gladkov
2020-08-04 18:52             ` Oleg Nesterov
2020-08-04 19:33             ` Luc Van Oostenryck
2020-08-04 20:02             ` Luc Van Oostenryck
2020-08-05 10:16               ` Alexey Gladkov
     [not found] <note_185299@salsa.debian.org>
     [not found] ` <note_185431@salsa.debian.org>
     [not found]   ` <note_185453@salsa.debian.org>
     [not found]     ` <note_185458@salsa.debian.org>
     [not found]       ` <note_185460@salsa.debian.org>
     [not found]         ` <note_185461@salsa.debian.org>
     [not found]           ` <note_185530@salsa.debian.org>
     [not found]             ` <note_185532@salsa.debian.org>
     [not found]               ` <20200805110418.iutr56vyewhbqr7v@ltop.local>
     [not found]                 ` <20200805112141.ier2xkhm5sqjtbck@comp-core-i7-2640m-0182e6>
2020-08-05 15:20                   ` Luc Van Oostenryck
2020-08-05 15:44                     ` Alexey Gladkov
2020-08-05 19:58                       ` Luc Van Oostenryck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200802213035.w7bexg4zdusr25xf@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=gitlab+9b7df497d06cab14c2bf3c1022d8ca15@salsa.debian.org \
    --cc=gladkov.alexey@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).