13:43 <uwumeowmeownyaa> Recently I've spent two days configurin a Debian GNU/Linux distribution to suit my needs. How long would it take me to configure CRUX GNU/Linux to achieve the same result?

13:44 <uwumeowmeownyaa> By two days I mean 6 and 8 hours respectively.

13:57 <darfo_> What is the airspeed velocity of an unladen swallow?

14:13 <jaeger> I would guess somewhat less than the first time since you've already done it now, offset by how much time it takes to compile whatever packages you need.

14:49 <SiFuh> darfo_: Heh, Monty Python

19:01 <ppetrov^> guys. I am cleaning up my ports and dealing with python stuff at the moment. When is it advisable to have the "python3-" prefix for the port/package?

19:02 <cruxbot> [compat-32/3.7]: curl-32: 8.9.1 -> 8.10.1

19:02 <cruxbot> [compat-32/3.7]: gst-plugins-base-32: 1.24.7 -> 1.24.8

19:02 <cruxbot> [compat-32/3.7]: gstreamer-32: 1.24.7 -> 1.24.8

19:02 <cruxbot> [xorg/3.7]: mesa: 24.2.2 -> 24.2.3

19:02 <cruxbot> [compat-32/3.7]: mesa-32: -> 24.2.2

19:03 <cruxbot> [contrib/3.7]: python3-django-allauth: 64.2.0 -> 64.2.1

19:03 <cruxbot> [opt/3.7]: bindutils: 9.20.1 -> 9.20.2

19:03 <cruxbot> [compat-32/3.7]: pipewire-32: 1.2.3 -> 1.2.4

19:03 <cruxbot> [contrib/3.7]: python3-sqlalchemy: 2.0.34 -> 2.0.35

19:03 <cruxbot> [opt/3.7]: btrfs-progs: 6.10.1 -> 6.11

19:03 <cruxbot> [contrib/3.7]: python3-zope-i18nmessageid: 6.1.0 -> 7.0

19:03 <cruxbot> [opt/3.7]: ppp: 2.5.0 -> 2.5.1

19:03 <cruxbot> [contrib/3.7]: gst-plugins-bad: 1.24.7 -> 1.24.8

19:03 <cruxbot> [opt/3.7]: gst-libav: 1.24.7 -> 1.24.8

19:03 <cruxbot> [contrib/3.7]: gst-plugins-good: 1.24.7 -> 1.24.8

19:03 <cruxbot> [opt/3.7]: gst-plugins-base: 1.24.7 -> 1.24.8

19:03 <cruxbot> [contrib/3.7]: gst-plugins-ugly: 1.24.7 -> 1.24.8

19:03 <cruxbot> [opt/3.7]: gstreamer: 1.24.7 -> 1.24.8

19:03 <cruxbot> [contrib/3.7]: gst-python3: 1.24.7 -> 1.24.8

19:03 <cruxbot> [opt/3.7]: libzip: 1.10.1 -> 1.11.1

19:03 <cruxbot> [contrib/3.7]: loki: 3.1.1 -> 3.2.0

19:03 <cruxbot> [contrib/3.7]: ostree: 2024.7 -> 2024.8

19:03 <cruxbot> [contrib/3.7]: pipewire: 1.2.3 -> 1.2.4

19:03 <cruxbot> [contrib/3.7]: python3-pyproject-api: 1.7.2 -> 1.8.0

19:03 <cruxbot> [contrib/3.7]: python3-tox: 4.19.0 -> 4.20.0

19:03 <cruxbot> [contrib/3.7]: python3-treq: 23.11.0 -> 24.9.0

19:03 <cruxbot> [contrib/3.7]: python3-zope-hookable: 6.0 -> 7.0

19:03 <cruxbot> [contrib/3.7]: seahorse: 43.0 -> 47.0.1

19:04 <cruxbot> [contrib/3.7]: zoxide: 0.9.5 -> 0.9.6

19:05 <SiFuh> ppetrov^: Hahaha ^

19:07 <ppetrov^> mhm

19:12 <jaeger> I don't remember the history there but I assume it was just to distinguish that a module was specific to python 3 vs 2 at the time. Just a convention now, I think, but like I said, don't remember for sure

19:13 <SiFuh> I don't think it will be changed. Most probably out of habit now.

19:14 <ppetrov^> so the "python3-" is traditionally meant for python modules, while "larger" python programs are named "normally"

19:15 <jaeger> That's my general take on it

19:15 <ppetrov^> ok, thanks

19:16 <ppetrov^> jaeger, is python2 is removed from 3.8, then will these all be renamed to python-*, similar to what Arch has?

19:17 <ppetrov^> (no idea why i am so interested in the naming convention all of a sudden...)

19:17 <jaeger> Not sure we've talked about it yet. It would be some work

19:18 <ppetrov^> best of luck

19:19 <SiFuh> ppetrov^: Imagine the work alan must do.

19:19 <ppetrov^> is he active?

19:19 <SiFuh> As far as I know, yes

19:19 <ppetrov^> cool

19:19 <SiFuh> His ports are a bit of a mess though.

19:19 <ppetrov^> nobody's perfect

19:27 <SiFuh> Guinness time.

19:52 <cruxbot> [compat-32/3.7]: mesa-32: 24.2.2 -> 24.2.3