From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cups: deprecate package due to security issues
Date: Fri, 06 Mar 2015 11:30:29 -0300 [thread overview]
Message-ID: <54F9BA05.9050702@zacarias.com.ar> (raw)
In-Reply-To: <20150306150950.0fbaa59e@free-electrons.com>
On 03/06/2015 11:09 AM, Thomas Petazzoni wrote:
> Any reason why this is done on the comment only, and not on the package
> itself?
>
> Other than that, I'd personally be in favor of this deprecation.
> Hopefully it will encourage someone to step up and upgrade cups.
I just used it as a mark for when/if removing it, since they all depend
on BR2_PACKAGE_CUPS being selected, not needed really.
Ideally something like BR2_LEGACY would be best for the users to get a
big warning, problem is that introducing it for just one package isn't
very useful, and it would set a precedent for other packages to lag
behind as well.
Regards.
next prev parent reply other threads:[~2015-03-06 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 13:39 [Buildroot] [PATCH] cups: deprecate package due to security issues Gustavo Zacarias
2015-03-06 14:09 ` Thomas Petazzoni
2015-03-06 14:30 ` Gustavo Zacarias [this message]
2015-03-07 0:37 ` [Buildroot] Adding deprecated packages to legacy [was: cups: deprecate package due to security issues] Arnout Vandecappelle
2015-03-16 21:26 ` [Buildroot] [PATCH] cups: deprecate package due to security issues Thomas Petazzoni
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=54F9BA05.9050702@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.