Bug#632438: [Popcon-developers] Bug#681721: #632438:
popularity-contest: a way to exclude certain packages
Message-Id: <20200920200835.682a9d43e058cc71a15a62fe@xdump.org>
In-Reply-To: <[🔎] 20200920090418.GC23508@yellowpig>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
On Sun, 20 Sep 2020 11:04:18 +0200 Bill Allombert <ballombe@debian.org> wrote:
> On Sun, Sep 20, 2020 at 01:12:56PM +0900, Kentaro Hayashi wrote:
> > Control: tags -1 patch
> >
> > Hi,
> >
> > I've attached a simple PoC patch to exclude certain packages.
> > patch is generated against 1.70.
> >
> > It may be better spec or implementation, but just works for me.
>
> Dear Kentaro,
> Could you explain why you want to exclude some package ?
> I am concerned this will squew the statistic, if used indiscriminately.
I want to exclude installed packages from 3rd party vendor
such as /etc/apt/sources.list.d/*.list. (some may be proprietary software)
> Instead I would suggest to add a new dpkg control field 'X-Popcon: private' and
> have popularity-contest skip packages having this field.
I will appreciate this idea.
If the packages are under my control, I could add 'X-Popcon: private',
but not for 3rd party vendor's package every updates, I think.
> This way users will be able to create private packages that will never
> register even on misconfigured hosts.
So I think that BOTH of approach is appropriate.
1. Add (popularity-contenst) configuration option to exclude specific
packages (such as 3rd party packages)
I've atached a PoC patch.
2. Use 'X-Popcon: private' for private packages.
Regards,
Reply to: