Mucking about with microframeworks

Posted Jul 10, 2019 20:21 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)
In reply to: Mucking about with microframeworks by Sesse
Parent article: Mucking about with microframeworks

Unless you need a newer version that is not packaged by your distro.

to post comments

Mucking about with microframeworks

Posted Jul 11, 2019 9:30 UTC (Thu) by smurf (subscriber, #17840) [Link] (2 responses)

So you package it yourself and upload to your site-local archive. For most Python modules, this process anything but rocket science.

Mucking about with microframeworks

Posted Jul 11, 2019 9:56 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link] (1 responses)

I honestly have no idea how to do this, and how to manage a local package archive. Ubuntu PPAs were the closest to that.

Quick googling also doesn't fill me with confidence about the ease of doing it.

Mucking about with microframeworks

Posted Jul 20, 2019 19:28 UTC (Sat) by garloff (subscriber, #319) [Link]

Open Build Service is a very efficient way to get it done.
https://build.opensuse.org/
Before you dismiss b/c it sounds like it's SUSE focused: It builds RPMs and DEBs for a large set of Linux distros (and many architectures, though most Py packages are noarch).

Mucking about with microframeworks

Posted Jul 11, 2019 14:32 UTC (Thu) by mirabilos (subscriber, #84359) [Link] (5 responses)

Just target Debian stable and do with the older versions. You don’t really need that new feature right now, and you’ll get all the security fixes still.

Mucking about with microframeworks

Posted Jul 11, 2019 14:48 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link] (2 responses)

>You don’t really need that new feature right now

How did you get to conclude that?

Mucking about with microframeworks

Posted Jul 11, 2019 15:03 UTC (Thu) by mirabilos (subscriber, #84359) [Link] (1 responses)

You don’t. You’re creating your own new software, and thus you can program it in a way that it does not depend on that shiny new feature not available in stable yet. (Or simply embed a backport in your own code, added when run on older stable distros.)

Mucking about with microframeworks

Posted Jul 11, 2019 15:19 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]

>. You’re creating your own new software, and thus you can program it in a way that it does not depend on that shiny new feature not available in stable yet.

You are asking developers to limit themselves to match a single slow moving distribution's schedule. History has clearly shown us that it is not going to work. Distributions will simply get bypassed

Mucking about with microframeworks

Posted Jul 11, 2019 18:37 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link] (1 responses)

Yeah, a great advice. I'm starting to think that the Windows approach (no package manager whatsoever) is actually the superior one.

Mucking about with microframeworks

Posted Jul 11, 2019 19:54 UTC (Thu) by rodgerd (guest, #58896) [Link]

The approach of a slow-moving, stable OS layer, with a high rate of change applications does seem to be what users want, with a mechanism for app discovery (Apple App Store, Windows Store, etc). This is what SuSE (OBS) and Canonical and Fedora (their respective Flatpack etc) seem to be trying to emulate.