Re: [py3porters-devel] Python 2 in the default installation -- progress made!

2017-01-02 Thread Daniel Kahn Gillmor
On Mon 2017-01-02 19:47:00 -0500, Ansgar Burchardt wrote:
> There was an open bug about changing the overrides (#849903) and I just
> set all packages built from gpgme1.0 to "Priority: optional".
>
> I don't think there is any reason for the lib*-dev packages to be at
> Priority: extra?

I read:

https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities

as suggesting that -dev packages are generally more "extra-ish" than
"optional", but then again, i think of workstations set up for software
development as having "specialized requirements" compared with what most
computers might reasonably want to install:

>>   optional
>> 
>>  (In a sense everything that isn't required is optional, but that's
>>  not what is meant here.) This is all the software that you might
>>  reasonably want to install if you didn't know what it was and don't
>>  have specialized requirements. This is a much larger system and
>>  includes the X Window System, a full TeX distribution, and many
>>  applications. Note that optional packages should not conflict with
>>  each other.
>> 
>>   extra
>> 
>>  This contains all packages that conflict with others with required,
>>  important, standard or optional priorities, or are only likely to
>>  be useful if you already know what they are or have specialized
>>  requirements (such as packages containing only detached debugging
>>  symbols).

I personally develop software, and i maintain many computers (for
myself, even), and i definitely *don't* want most of my computers to
include the -dev packages.

I'm happy to go with whatever the ftp-master team prefers, though. :)

 --dkg


signature.asc
Description: PGP signature


Re: [py3porters-devel] Python 2 in the default installation -- progress made!

2017-01-02 Thread Ansgar Burchardt
Daniel Kahn Gillmor writes:
> On Thu 2016-12-29 23:41:39 -0500, Stuart Prescott wrote:
>> one of the objectives for stretch was to reduce the number of Python 2
>> packages that are installed in common scenarios, instead having the
>> Python 3 stack take over. The "standard task" within tasksel is a
>> reasonable place to look.¹
>  [...]
>> python-gpg
>> python3-gpg
>
> fwiw, python-gpg and python3-gpg should not be Priority: standard, and
> they are indicated as such in the source packages.
>
>https://packages.qa.debian.org/g/gpgme1.0.html
>
> indicates that they're marked that way due to override files, but i
> don't think there'd be any objection from myself or any of the other
> pkg-gnupg-maint team (cc'ed here) if those overrides were removed.

There was an open bug about changing the overrides (#849903) and I just
set all packages built from gpgme1.0 to "Priority: optional".

I don't think there is any reason for the lib*-dev packages to be at
Priority: extra?

Ansgar



Re: [py3porters-devel] Python 2 in the default installation -- progress made!

2017-01-02 Thread Daniel Kahn Gillmor
On Thu 2016-12-29 23:41:39 -0500, Stuart Prescott wrote:
> one of the objectives for stretch was to reduce the number of Python 2
> packages that are installed in common scenarios, instead having the
> Python 3 stack take over. The "standard task" within tasksel is a
> reasonable place to look.¹
 [...]
> python-gpg
> python3-gpg

fwiw, python-gpg and python3-gpg should not be Priority: standard, and
they are indicated as such in the source packages.

   https://packages.qa.debian.org/g/gpgme1.0.html

indicates that they're marked that way due to override files, but i
don't think there'd be any objection from myself or any of the other
pkg-gnupg-maint team (cc'ed here) if those overrides were removed.

--dkg


signature.asc
Description: PGP signature