41–50 of 103 posts
Can anybody explain me what is the purpose of the element-desktop-bin package? It just takes the binary from the packages.riot.im repo. That's what I do, too, by having packages.riot.im in my sources.list.d. Why repackage it?
Earlier quoted context omitted.
So you would rather have them waste that exact same amount of space on every computer, just so you don’t have to download it when you want to build a package?
I don't have any Debian machine that doesn't end up with build-essential and dozens of header packages installed; it just comes up too often. Adding the header files directly to the packages saves time and frustration, and probably even saves space since a lot these packages are 50% overhead (dpkg meta files, db entries, etc.) by size.
Earlier quoted context omitted.
It's okay to ride a bicycle instead of a car, or vice versa. It's not okay to put bicycle tires on a car, or a car transmission on a bicycle. I have no complaints about distros that are either 100% systemd or 100% init scripts. The problem with Debian (and its derivatives) is that they're trying to maintain both at the same time. If they really want to support both "/etc/init.d/servicename start" and "systemctl start…
In fact, init scripts are only used by systemd when there are no corresponding native unit files.
I'm excited to see someone is working on this. I have considered switching from Arch to Sid in the past, mainly so that I could run the same OS on all computers and because I like the DFSG. Two things have stopped me: * It's so much harder to build your own software packages on Debian. Even patching an existing Debian package can be painful, and having to write your own packages is even worse. I'm sure a dedicated en…
If I want to try running a Debian package with an experimental patch as a one-off, I haven't found it too hard to build my own version.
But AFAIK there's nothing that helps me manage the necessary work to rebuild with the same patch when a new distribution version comes along.
Do source-based distributions have a good solution for this?
I think this is great. I am an arch user at home, but at work I use Ubuntu. It is really difficult sometimes to get the latest version of a software installed in an easy way. I tend to use a lot of custom Makefiles for this, but I don't really like to not use the package manager. Being an arch user, I always wished it was as easy to build deb packages as it is to build packages with makepkg. I tried the debian way, a…
At home I've switched fully to NixOS.
Linux does not need more package managers. It creates nothing but support burdens and busywork for developers (yes, user repositories too). I don't understand what people expect to achieve by further fragmenting a minority OS that makes up only 3% of Desktop users.
- Market share is not the most important metric, resilience matters and Linux distributions have only gained in acceptance over years - People have a fear or even aversion toward experiments since it needs effort, but some folks are simply geeks - they will keep trying and more power to them - Some of these experiments, historically, have brought some of the best open innovations in the industry and moved even closed…
I really wish we could have an open-source OS that was reliable and user-friendly for consumers (especially given how user-hostile Windows has become in the last 5 years), while similarly being non-burdensome for devs to deploy software to (which, to be fair, has improved a lot recently thanks to AppImageKit et al).
I'm excited to see someone is working on this. I have considered switching from Arch to Sid in the past, mainly so that I could run the same OS on all computers and because I like the DFSG. Two things have stopped me: * It's so much harder to build your own software packages on Debian. Even patching an existing Debian package can be painful, and having to write your own packages is even worse. I'm sure a dedicated en…
The inconvenience goes further than building in the first place. If I want to try running a Debian package with an experimental patch as a one-off, I haven't found it too hard to build my own version. But AFAIK there's nothing that helps me manage the necessary work to rebuild with the same patch when a new distribution version comes along. Do source-based distributions have a good solution for this?
Earlier quoted context omitted.
In fact, init scripts are only used by systemd when there are no corresponding native unit files.
A lot of debian packages supply both systemd unit files and init scripts. You can use either to step on the other's foot.
Linux does not need more package managers. It creates nothing but support burdens and busywork for developers (yes, user repositories too). I don't understand what people expect to achieve by further fragmenting a minority OS that makes up only 3% of Desktop users.