Re: [arch-dev-public] Speaking of OCaml: willing to orphan merlin + deps

Le 18/08/2019 à 08:16, Jürgen Hötzel a écrit : > Hi, > > Bruno Pagani via arch-dev-public writes: > >> orphan merlin (OCaml smart auto-completion for emacs/vim) and its >> dependency tree as I’m no longer using any of those and don’t expect to >> use them

[arch-dev-public] Speaking of OCaml: willing to orphan merlin + deps

Hi there, I’m riding on the train of OCaml e-mails to announce that I’m going to orphan merlin (OCaml smart auto-completion for emacs/vim) and its dependency tree as I’m no longer using any of those and don’t expect to use them again: – cppo – dune – menhir – merlin – ocaml-biniou –

Re: [arch-dev-public] Create guidelines regarding SIMD instructions/x86 extensions

Le 25/05/2019 à 13:27, Allan McRae via arch-dev-public a écrit : > On 25/5/19 9:19 pm, Bruno Pagani via arch-dev-public wrote: >> Hi, >> >> Le 25/05/2019 à 02:17, Filipe Laíns via arch-dev-public a écrit : >>> I would also like to explore the idea of adding an "

Re: [arch-dev-public] Create guidelines regarding SIMD instructions/x86 extensions

Hi, Le 25/05/2019 à 02:17, Filipe Laíns via arch-dev-public a écrit : > I would also like to explore the idea of adding an "high performance" > architecture which would be able to make use of SSE{,2,3,4,4.1,4.2} and > AVX, which seem to be the standard for newer processors (>=2013). This > would

Re: [arch-dev-public] Follow-up on the “Proposal: minimal base system”

Le 17/03/2019 à 23:13, Gaetan Bisson via arch-dev-public a écrit : > [2019-03-17 19:07:23 +0100] Bruno Pagani via arch-dev-public: >> This is a follow-up on the last month discussion about a “minimal base >> system”. > Creating a new thread removed from the discussion we had

[arch-dev-public] Follow-up on the “Proposal: minimal base system”

Hi there, This is a follow-up on the last month discussion about a “minimal base system”. # Reminder of the starting statement > There is no strict definition of what a minimal Arch Linux system installation must contain. However in reality we mostly don’t add any packages that are in the base

Re: [arch-dev-public] Proposal: minimal base system

Le 12/02/2019 à 19:16, Gaetan Bisson a écrit : > [2019-02-12 16:40:08 +0100] Bruno Pagani via arch-dev-public: >> Just in case it wasn’t clear, my answer would have been mostly the same >> as Eli’s. >> >> So, Gaetan, Allan and Bartłomiej (or anyone else for that matt

Re: [arch-dev-public] Proposal: minimal base system

let us first >> turn [base] into something useful, and only then wonder if we need >> something more. >> >> >> [2019-02-05 14:38:26 +0100] Bruno Pagani via arch-dev-public: >>> Le 05/02/2019 à 12:54, Allan McRae a écrit : >>>> If someone knows they w

Re: [arch-dev-public] Proposal: minimal base system

Le 05/02/2019 à 12:54, Allan McRae a écrit : > On 5/2/19 9:06 pm, Bruno Pagani wrote: >> Le 22/01/2019 à 00:59, Allan McRae a écrit : >>> On 22/1/19 9:41 am, Bruno Pagani wrote: Le 22/01/2019 à 00:23, Allan McRae via arch-dev-public a écrit : > On 22/1/19 8:03 am, Levente Polyak via

Re: [arch-dev-public] Proposal: minimal base system

Le 22/01/2019 à 14:44, Bartłomiej Piotrowski via arch-dev-public a écrit : > On 22/01/2019 00.23, Allan McRae via arch-dev-public wrote: >> On 22/1/19 8:03 am, Levente Polyak via arch-dev-public wrote: >>> Everything that won’t be part of base-system needs to be added as a >>> dependency to all

Re: [arch-dev-public] Proposal: minimal base system

Le 22/01/2019 à 00:59, Allan McRae a écrit : > On 22/1/19 9:41 am, Bruno Pagani wrote: >> Le 22/01/2019 à 00:23, Allan McRae via arch-dev-public a écrit : >>> On 22/1/19 8:03 am, Levente Polyak via arch-dev-public wrote: Everything that won’t be part of base-system needs to be added as a

Re: [arch-dev-public] Proposal: minimal base system

Le 22/01/2019 à 03:25, Gaetan Bisson via arch-dev-public a écrit : > [2019-01-21 18:58:54 -0500] Eli Schwartz via arch-dev-public: >> On 1/21/19 6:53 PM, Giancarlo Razzolini via arch-dev-public wrote: >>> I agree with this package list. It's missing mkinitcpio though. >> No it is not, mkinitcpio

Re: [arch-dev-public] Proposal: minimal base system

Le 22/01/2019 à 00:23, Allan McRae via arch-dev-public a écrit : > On 22/1/19 8:03 am, Levente Polyak via arch-dev-public wrote: >> Everything that won’t be part of base-system needs to be added as a >> dependency to all requiring packages; alternatively don't omit any first >> level runtime

Re: [arch-dev-public] Orphaning some more packages

Le 26/11/2018 à 15:08, Bruno Pagani a écrit : > Hi there, > > I’m orphaning two set of packages that I no longer use: > > – adapta-kde/kvantum-theme-adapta split package: very low maintenance, > especially since upstream Adapta is stalled; > > – merlin and its dependencies: cppo, dune, merlin,

[arch-dev-public] Orphaning adapta-kde and merlin tree

Hi there, I’m orphaning two set of packages that I no longer use: – adapta-kde/kvantum-theme-adapta split package: very low maintenance, especially since upstream Adapta is stalled; – merlin and its dependencies: cppo, dune, merlin, ocaml-biniou, ocaml-easyformat, ocaml-yojson. Those have

Re: [arch-dev-public] TU application process

Le 06/11/2018 à 11:37, Allan McRae a écrit : > On 6/11/18 8:15 pm, Bruno Pagani wrote: >> Le 06/11/2018 à 11:12, Christian Rebischke via arch-dev-public a écrit : >>> On Tue, Nov 06, 2018 at 08:09:03PM +1000, Allan McRae wrote: On 6/11/18 7:54 pm, Christian Rebischke via arch-dev-public

Re: [arch-dev-public] TU application process

Le 06/11/2018 à 11:12, Christian Rebischke via arch-dev-public a écrit : > On Tue, Nov 06, 2018 at 08:09:03PM +1000, Allan McRae wrote: >> On 6/11/18 7:54 pm, Christian Rebischke via arch-dev-public wrote: >>> Hello everybody, >>> >>> First of all, the following mail has nothing to do with the

Re: [arch-dev-public] Dropping KDE4 libs

Le 25/08/2018 à 01:31, Gaetan Bisson a écrit : > [2018-08-24 18:45:33 +0200] Bruno Pagani: >> I have a ready PKGBUILD >> (https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=scribus-devel) >> that I can push (after changing the pkgname) if scribus is moved to >> [community]. And we can

Re: [arch-dev-public] Dropping KDE4 libs

Le 24/08/2018 à 18:38, Gaetan Bisson via arch-dev-public a écrit : > [2018-08-24 11:51:30 +0200] Bruno Pagani via arch-dev-public: >>> scribus >> The develop branch (1.5.x), available as scribus-devel in the AUR (and >> maintained by myself), is Qt5. It has been in de

Re: [arch-dev-public] Dropping KDE4 libs

Le 24/08/2018 à 11:10, Antonio Rojas via arch-dev-public a écrit : > fcitx-qt4 > ibus-qt The first one will be useless once Qt4 apps are gone, the second one can be rebuild without Qt4 support when that happens too. > keepassx > keepassx2 I think both should be dropped as replaced by

Re: [arch-dev-public] Dropping KDE4 libs

Le 17/08/2018 à 20:53, Antonio Rojas via arch-dev-public a écrit : > I think it's time to drop the KDE4 libraries. They were EOL months ago and > most stuff that isn't yet ported to KF5 is dead upstream. This would allow > dropping a number of qt4 libraries and reduce the qt4 reverse

Re: [arch-dev-public] Dropping pyqt4/pyside1

Le 17/08/2018 à 20:39, Antonio Rojas via arch-dev-public a écrit : > Hi all, > The latest pyqt4 release makes packaging more complex due to upstream's > decision of requiring a private namespaced sip (for mysterious reasons). It > is also the last release, so pyqt4 is now officially EOL. I

Re: [arch-dev-public] dropping luxrender packages

Le 27/07/2018 à 19:59, Lukas Jirkovsky via arch-dev-public a écrit : > Hi, > I'd like to drop the luxrays, luxrender and luxblend25 packages from > [community]. They have always required continuous attention to keep > working which I can no longer provide with sufficient quality and > right now

Re: [arch-dev-public] Removing 'orphan' python2 modules

Le 27/06/2018 à 21:51, Antonio Rojas via arch-dev-public a écrit : >> Please reply if you have objections. >> A list of modules / programs can be obtained as following or viewed here > That list doesn't take makedepends/optdepends into account. There are a few > optdepends of sagemath there

Re: [arch-dev-public] Automatic Signing of ISOs, pacman databases and everything else (was: Arch Linux Cloud Images (virtualbox and Qemu))

Le 15/05/2018 à 17:25, Florian Pritz via arch-dev-public a écrit : > On 13.05.2018 22:47, Christian Rebischke via arch-dev-public wrote: >> We could just generate an automated cloud image signing key (only for >> this purpose) of course and automatically sign the images with that key. >> Problem

Re: [arch-dev-public] RFC: Dropping -DCMAKE_BUILD_TYPE from packages using cmake

Le 13/03/2018 à 13:42, Antonio Rojas via arch-dev-public a écrit : > El martes, 13 de marzo de 2018 11:23:07 (CET) Bruno Pagani via > arch-dev-public escribió: >> Some projects seems to default to Debug instead of None… So should we >> specify a BUILD_TYPE of None

Re: [arch-dev-public] RFC: Dropping -DCMAKE_BUILD_TYPE from packages using cmake

Le 11/03/2018 à 10:00, Antonio Rojas via arch-dev-public a écrit : > El domingo, 11 de marzo de 2018 1:44:07 (CET) Eli Schwartz via > arch-dev-public escribió: >> This theoretically sounds like a fantastic idea, but I'm not really sure >> what CMake's deal with build flags are in the first

Re: [arch-dev-public] RFC: Dropping -DCMAKE_BUILD_TYPE from packages using cmake

Le 10/03/2018 à 11:34, Antonio Rojas via arch-dev-public a écrit : > Hi, > Currently most of our packages which use the cmake build system are built > with -DCMAKE_BUILD_TYPE=Release. This provides a reasonable (according to > upstream) set of C(XX)FLAGS defaults which are appended to and

Re: [arch-dev-public] 2017 repository cleanup

Le 03/01/2018 à 23:31, Balló György via arch-dev-public a écrit : > You missed some optional and indirect dependencies. TBH, he explicitly stated not having included optional dependencies. But I agree that missing them is an issue. ;) Regards, Bruno signature.asc Description: OpenPGP digital

Re: [arch-dev-public] 2017 repository cleanup

Le 18/12/2017 à 10:54, Bartłomiej Piotrowski via arch-dev-public a écrit : > - flickcurl: > Archange: darktable Took it. > - ftjam: > eric: lincity-ng > jlichtblau: lincity-ng > svenstaro: megaglest > Archange: argyllcms > - js185: > Archange: couchdb Erm… Took them,

Re: [arch-dev-public] 2017 repository cleanup

Le 18/12/2017 à 21:48, Jelle van der Waa a écrit : > On 12/18/17 at 10:47am, Gaetan Bisson via arch-dev-public wrote: >> [2017-12-18 10:54:37 +0100] Bartłomiej Piotrowski via arch-dev-public: >>> - tclap: >>> bisson: hugin >> I've just orphaned hugin too. Happy adopting! :) > Gotta catch them

Re: [arch-dev-public] systemd - move to base group and expect it to be installed?

Le 12/09/2017 à 21:27, Giancarlo Razzolini a écrit : > Em setembro 12, 2017 14:58 Andreas Radke escreveu: >> New filesystem/systemd packages in testing have changed the way we >> create system users/groups. That's done now via systemd itself or using >> a systemd hook. So every package that needs

Re: [arch-dev-public] switching to systemd-stable

Le 01/07/2017 à 20:15, Laurent Carlier via arch-dev-public a écrit : > Le samedi 1 juillet 2017, 19:59:49 CEST Christian Hesse a écrit : >> Dave Reisner on Sat, 2017/07/01 13:22: >>> One potentially bikeshed-worthy question is versioning. Do we count >>> commits and modify

Re: [arch-dev-public] Mesa, Nvidia and libglvnd (the good, the bad and the ugly) :)

Hi, Thanks for thinking about libglvnd support in Arch. ;) Le 12/02/2017 à 19:22, Laurent Carlier via arch-dev-public a écrit : > Bumblebee will not work anymore with Nvidia and Mesa, but only with prime (1). This sentence doesn’t really make sense. Bumblebee doesn’t work with PRIME, they are