Live data from Hacker News

Debian Packages That Need Lovin'

wnpp.debian.net

141–150 of 151 posts

Re: Debian Packages That Need Lovin'

#141
post #70

As someone who's thinking about moving to Linux and has made many non-trivial contributions to Homebrew, the contribution process for Debian packages scares me. The official documentation seems to be more of a reference guide than a tutorial, and community blog posts always seem to start with "That other tool is outdated; here's the new way to do it," making it impossible to know which method is the right one. IMO, w…

Debian packaging being complex, there are many documentations around it. Packaging practices also change, but it's difficult to know which documentation is up-to-date or not. However, the very official documentation from the project is kept up-to-date: https://www.debian.org/doc/manuals/maint-guide/ and https://www.debian.org/doc/manuals/developers-reference/ . But, yes, they are long and only cover the basics. There…

Please note that maint-guide is considered deprecated by its author, who has switched to debmake-doc.

Re: Debian Packages That Need Lovin'

#143
post #56

Earlier quoted context omitted.

Well, you need to get competent enough before you take on a role as package maintainer. For start, imagine that you are one. First, choose a package that really matters to you. On a daily basis. A package that you yourself would NEED to have it up2date the next day a new version is out. Get the source deb and try to build it. Usually it's not very hard. Then, try to do the same on all the debian variants (unstable, s…

That does seem like it would be a sensible way of going about things if I could manage to find a package of modest complexity that is important to me, but under-maintained.

I a good way to find things you use that need help is the how-can-i-help tool:

https://wiki.debian.org/how-can-i-help

Re: Debian Packages That Need Lovin'

#145

Earlier quoted context omitted.

I've been thinking about leaving Fedora and your comment intrigues me. Does Zoom work well with i3? Can you share your screen? Regarding PulseAudio, I didn't realize Linux users had a choice about whether to use it - is there an alternate audio subsystem available?

> Does Zoom work well with i3? Can you share your screen? Yes and yes. Source: I run Zoom with i3.

Do you happen to know if Zoom is available on FreeBSD?

Re: Debian Packages That Need Lovin'

#146
post #120

Packaging for debian anything non trivial is damn too hard. It took me 5 days to figure out how to package a complete web app with params, upgrades, post install transpiling, db init, etc. And I haven't put that on a private repo yet, it's yet another annoying thing to do. Nothing is well documented, doc is old and confusing, the tooling is archaic and wants to inflict pain (debconf anyone ?), the life cycle of a Deb…

On the other hand, Debian is a large community of volunteers providing a distro on democratic principles for a long time successfully. Comparable distros are either companies (Ubuntu, RedHat, SuSE) or heroic deeds of one or few people (Slackware). I find that an amazing even if it is heavily burdened by technical debt these days.

Oh, sure.

But that's beyond the point that if what they really desire is contribution, which they have been claiming for years, they should make it less painful to package software for the plateform, which we have been claiming for years.

Re: Debian Packages That Need Lovin'

#147
post #128

Packaging for debian anything non trivial is damn too hard. It took me 5 days to figure out how to package a complete web app with params, upgrades, post install transpiling, db init, etc. And I haven't put that on a private repo yet, it's yet another annoying thing to do. Nothing is well documented, doc is old and confusing, the tooling is archaic and wants to inflict pain (debconf anyone ?), the life cycle of a Deb…

You have some points here, but the Bash part is _not_ the problem. Bash is everywhere and the true fix to that bit is to learn Bash: It's not hard and I benefit from my Bash skills everyday, it's one of the best things to invest even a bit in. Just don't write "actual software" in Bash.

Oh, but bash is definitively part of the problem.

I'm pretty proficient in bash myself, and error handling, debugging, decoupling and refactoring in bash are all horrible. It's just not design for being good at a script with more than a couple of lines. The fact we do use it for such purpose does not make it good at it.

The fact it has no namespace, the lack of decent data structures and the very limited functions also all leads to making it a poor foundation to build a lib on. Hence deb packages don't have any kind of framework for basic things: you are on your own.

Re: Debian Packages That Need Lovin'

#148
post #125

Packaging for debian anything non trivial is damn too hard. It took me 5 days to figure out how to package a complete web app with params, upgrades, post install transpiling, db init, etc. And I haven't put that on a private repo yet, it's yet another annoying thing to do. Nothing is well documented, doc is old and confusing, the tooling is archaic and wants to inflict pain (debconf anyone ?), the life cycle of a Deb…

I think many package managers take longer than a week to figure out. RPM is more difficult that deb, setuptools takes months to understand it fully and is changing constantly. Meson, Conan, winget+msi, and the hundreds of other mixtures of build system + package manager also take long to understand. And you have to understand each of them. Homebrew does not even want package authors to create packages themselves. It…

I'm not counting the research I did prior the 5 days to actually understand deb packaging, only the 5 days trying to package something.

Re: Debian Packages That Need Lovin'

#149

Packaging for debian anything non trivial is damn too hard. It took me 5 days to figure out how to package a complete web app with params, upgrades, post install transpiling, db init, etc. And I haven't put that on a private repo yet, it's yet another annoying thing to do. Nothing is well documented, doc is old and confusing, the tooling is archaic and wants to inflict pain (debconf anyone ?), the life cycle of a Deb…

As for building packages for your own use, the tooling is not that difficult. The documentation is just oriented to contribute packages for Debian itself. This implies some unwanted complexity and navigating outdated documentation. Packaging for Debian becomes simpler, but it's heavily rooted into having multiple files describing the package, use of a tarball as the source package and having each language comes with…

Thanks for this tutorial, it covers a lot.

Re: Debian Packages That Need Lovin'

#150

When you click on random (or not so random) packages like Libreoffice, it brings you to [0] where help was requested in 2007 and as recent as oct 2020 offers for help are ignored. Not sure how this 'process' works? [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419523

I'm a Debian developer. It can look a little chaotic from outside. But there are a few simple principles operating here. Mostly they follow from the Debian being a collection of 1000 developers, all equal. There is no CEO who can decide what's important and force someone to do something. Instead, Debian is a do'ocracy. If there is a dispute, it always takes the form of two Debian developers wanting to do something di…

I understood the second rule, but could you please explain the first rule more clearly? This idea of a do-ocracy is very interesting to me.
Post reply on HN