Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Sébastien Luttringer via arch-dev-public
On Sat, 2020-01-04 at 13:08 +1000, Allan McRae via arch-dev-public wrote: > On 4/1/20 12:47 pm, Sébastien Luttringer via arch-dev-public wrote: > > One unfortunate consequence could be to have packages rely on it to make > > dependencies shorter, and make us pull cups or cronie. > > What?! That

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Allan McRae via arch-dev-public
On 4/1/20 12:47 pm, Sébastien Luttringer via arch-dev-public wrote: > One unfortunate consequence could be to have packages rely on it to make > dependencies shorter, and make us pull cups or cronie. What?! That is like saying one unfortunate consequence of pamcan hooks is that packages can have

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Sébastien Luttringer via arch-dev-public
On Fri, 2020-01-03 at 11:11 -0500, Eli Schwartz via arch-dev-public wrote: > On 1/3/20 10:48 AM, Sébastien Luttringer wrote: > > On Thu, 2020-01-02 at 23:35 -0500, Eli Schwartz via arch-dev-public wrote: > > > ... > > > > > > Thoughts? > > > > I would argue that POSIX is a standard which people

Re: [arch-dev-public] Killing Python 2 (v2)

2020-01-03 Thread Ike Devolder via arch-dev-public
On 2/01/2020 17:24, Eli Schwartz via arch-dev-public wrote: > On 1/2/20 11:12 AM, Jelle van der Waa wrote: > >> # Remove python2 support >> >> * pycharm-community-edition - remove python2 support > > Seems reasonable to not encourage people to use python2 in an IDE these > days. > >> * vim -

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Eli Schwartz via arch-dev-public
On 1/3/20 10:48 AM, Sébastien Luttringer wrote: > > On Thu, 2020-01-02 at 23:35 -0500, Eli Schwartz via arch-dev-public wrote: >> ... >> >> Thoughts? > > Posix is an old standard which fail to make a common ground to Unix systems. > > If we think user needs meta packages to install their Arch,

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Eli Schwartz via arch-dev-public
On 1/3/20 10:22 AM, Santiago Torres-Arias via arch-dev-public wrote: > On Fri, Jan 03, 2020 at 03:49:11PM +0100, Robin Broda via arch-dev-public > wrote: >> On 1/3/20 5:35 AM, Eli Schwartz via arch-dev-public wrote: >>> After a bit of research work and making sure one or two things have been >>>

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Sébastien Luttringer via arch-dev-public
On Thu, 2020-01-02 at 23:35 -0500, Eli Schwartz via arch-dev-public wrote: > ... > > Thoughts? Posix is an old standard which fail to make a common ground to Unix systems. If we think user needs meta packages to install their Arch, is the Linux Standard Base more relevant to us? Cheers,

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Santiago Torres-Arias via arch-dev-public
On Fri, Jan 03, 2020 at 03:49:11PM +0100, Robin Broda via arch-dev-public wrote: > On 1/3/20 5:35 AM, Eli Schwartz via arch-dev-public wrote: > > After a bit of research work and making sure one or two things have been > > properly packaged, I've developed a PKGBUILD which ensures that a system >

Re: [arch-dev-public] Adding a "posix" metapackage

2020-01-03 Thread Robin Broda via arch-dev-public
On 1/3/20 5:35 AM, Eli Schwartz via arch-dev-public wrote: > After a bit of research work and making sure one or two things have been > properly packaged, I've developed a PKGBUILD which ensures that a system > has the POSIX shell and utilities (XCU) section installed. I believe > this is an

Re: [arch-dev-public] Killing Python 2 (v2)

2020-01-03 Thread Jelle van der Waa
On 01/02/20 at 11:18am, Santiago Torres-Arias via arch-dev-public wrote: > On Thu, Jan 02, 2020 at 05:12:33PM +0100, Jelle van der Waa wrote: > > > For packages still providing python2 functionality such as vim and > > others I propose we remove python2 support to actively to discourage > >

Re: [arch-dev-public] Killing Python 2 (v2)

2020-01-03 Thread Jelle van der Waa
On 01/02/20 at 07:09pm, keenerd via arch-dev-public wrote: > On 1/2/20, Jelle van der Waa wrote: > > * armagetronad - dead upstream, optional dep can be removed > > Fixed instead. It still works a treat. Thanks a lot! This was my hidden agenda all along ^_^ I've found many packages which have

Re: [arch-dev-public] Killing Python 2 (v2)

2020-01-03 Thread Rémy Oudompheng via arch-dev-public
Le jeu. 2 janv. 2020 à 17:12, Jelle van der Waa a écrit : > Hi All, > > 2020 happened and Python 2 is very much still alive, even worse there > will be an update in April. > > However we should actively strive to get rid of Python 2 before it. Some > upstreams are (still) working on porting to