I've been using Debian for over 10 years and I still love it as a user. But as a developer, I find it extremely frustrating. I've several times attempted to figure out how to package my open-source projects [1] [2] for Debian but the process is a nightmare. As I understand it, I first have to find someone with appropriate privileges to mentor me. I should be able to just submit a potential package for review. Then th…
> Then there is a ton of documentation on creating packages but which 300 page guide is the right one to use is unclear. And which set of packaging tools should I use? I've run into the same problems, though I've only wanted to build packages for my own use, or company-internal use. I think I've understood now how packaging is supposed to work, and have written a guide, shameless plug: http://leanpub.com/debian/c/hn…
Winding down my Debian involvement
191–200 of 238 posts
Re: Winding down my Debian involvement
#192I used debian for over 10 years and never managed to contribute anything. 10 Minutes after using homebrew for the first time I sent in a PR to update a package to the latest version and update the built dependencies.
And that's exactly why I use and trust Debian.
Re: Winding down my Debian involvement
#193Re: Winding down my Debian involvement
#19410+ year emeritus DD here -- Honestly I think "modern" dev culture is quite different from the core of he Debian community and this is both a strength and weakness. I can't say that I want Debian to look anything like the node ecosystem.
Thankfully, most companies (including FAANGs where I worked) are way more careful than that.
Flashy UIs change every day, really critical systems are kept very stable...
Re: Winding down my Debian involvement
#195I've been using Debian for over 10 years and I still love it as a user. But as a developer, I find it extremely frustrating. I've several times attempted to figure out how to package my open-source projects [1] [2] for Debian but the process is a nightmare. As I understand it, I first have to find someone with appropriate privileges to mentor me. I should be able to just submit a potential package for review. Then th…
Agreed, I've tried and failed to make Debian packages, and have no idea how to proceed. In contrast, with Gentoo and their documentation, it was straightforward for me to make my own additional, separate repo, look at other ebuilds to see how packaging works, and have everything just work. https://github.com/billsix/billsix-portage I submit ebuilds to Gentoo itself if I think others would benefit. As far as I can tel…
https://linuxconfig.org/easy-way-to-create-a-debian-package-...
And then a quality of life enhancement says push the package building off to FPM.
https://github.com/jordansissel/fpm
Personal Repo
https://www.digitalocean.com/community/tutorials/how-to-use-...
Re: Winding down my Debian involvement
#196Earlier quoted context omitted.
Yo! Trusted user from Arch Linux. >On the other side of the spectrum, I've found that the official binary repositories for Arch Linux suffer many of the same issues described in the article for Debian. Patches being ignored and collaboration or involvement being near impossible. Well, we still relay on svn internally so things are complicated to say the least. Even if we had things on git (which we are working on), I…
> I'm interested taking a look at this if you want :) I'd rather not, the thing in question was around three years ago and I don't think I even have my AUR PKGBUILD for comparison. It wasn't a cry for help, and I'm not naming packages or individuals for a reason. Just voicing some frustration at the process.
Re: Winding down my Debian involvement
#197Earlier quoted context omitted.
I'm not following the situation but what's stopping them from improving their packaging system, except for being complicated?
If the systemd discussion has taught me anything about Debian governance, getting everyone to agree is going to be a pain. Far easier to let it be.
Re: Winding down my Debian involvement
#198Earlier quoted context omitted.
Agreed, I've tried and failed to make Debian packages, and have no idea how to proceed. In contrast, with Gentoo and their documentation, it was straightforward for me to make my own additional, separate repo, look at other ebuilds to see how packaging works, and have everything just work. https://github.com/billsix/billsix-portage I submit ebuilds to Gentoo itself if I think others would benefit. As far as I can tel…
Probably won't help with Debian official packages but I've found success with these materials. https://linuxconfig.org/easy-way-to-create-a-debian-package-... And then a quality of life enhancement says push the package building off to FPM. https://github.com/jordansissel/fpm Personal Repo https://www.digitalocean.com/community/tutorials/how-to-use-...
This is the root of the Debian newbie community experience. FPM seems to get it at least.
Re: Winding down my Debian involvement
#199Earlier quoted context omitted.
> but random strangers not being allowed to push updates to my operating system in 5.34 seconds doesn’t sound all bad. To me. So that's what the frustrating to maintainers crumbling infrastructure and crappy tooling are for. Now it all makes sense! Actually, I'd very much prefer quickly pushed updates in case of severe security issues. Debian had lots of really ancient packages with problems in "stable" last time I l…
You're misunderstanding the point of Debian. Debian's "stable" release is that. Stable. No updates are issued for packages except for critical security updates, which are backported to the released version. It's essentially an LTS release. This isn't what everyone wants or needs, but if you do, Debian does it very well.
Re: Winding down my Debian involvement
#200Earlier quoted context omitted.
I don't mind RH being slower as I take it that's what makes RH what it is. Old packages but most stable.
It's not about RH packages directly. They are fine. As it is with universe on ubuntu, you quite likely need epel on rhel for doing quite a lot of basic stuff. If you are able to get by with just the proper supported packages in each distro, this doesn't affect you. And that's where the two diverge. universe is in better shape since it is semi-official, v/s epel which is completely unofficial/community-based.
The closest counterpart is SUSE's PackageHub, which is often seeded by stuff going into openSUSE Leap that isn't part of SLE itself.