61–70 of 238 posts
I've been using Debian / Ubuntu for many years, as much due to inertia and familiarity as anything else. And I have a lot of respect for the project. If I wanted to start being a contributor to a distribution, which one would be the best to dive in to?
The post shares several pain points with Debian's slow, aging change-process and integration-infrastructure. Open question: If Debian contributors feel the need to drop out and move on due to these pain points, are there less-painful Linux-distribution projects out there that are getting more of these pain points right they can flock to? Is this a sign that Debian needs to reform, or that other, newer distributions a…
I like Debian, but I agree it's become too slow and bureaucratic. Sadly, like most big organizations, it is hard to implement changes from inside. In my opinion, most Debian's issues stem from a centralized imperative package manager where all packages need to be carefully kept in sync for things to work. Moving to something like Nix would greatly simplify development. This is far from a new idea. In fact, it was qui…
When I first used Debian in the 90s it had a reputation for being slow and bureaucratic.
Earlier quoted context omitted.
That falsely presupposes that only people with poor quality bug reports would be put off from reporting bugs due to the interface. I've known people who can provide high quality, detailed bugs, decide not to because the extra hassles in reporting to Debian just aren't worth it to them.
No, it assumes that quality ratio varies by reporting mechanism. 9 good reports and 1 bad report are better than 18 good reports and 82 bad reports.
Personally, I'm annoyed at Debian still not having a Web frontend for bug filing. Practically all other distros have some kind of issue tracker site that allows filing bugs through it. Using reportbug or e-mail feels way less comfortable in comparison.
Better have fewer high quality bug reports than more low quality reports. The latter just teaches you to ignore them.
You're the guy behind i3? Thank you very much. I love it.
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? In the end, the time investment required to get started has kept me from contributing.
Instead, currently, all packages become lint-unclean, all maintainers need to read up on what the new thing is, how it might break, whether/how it affects them, manually run some tests, and finally decide to opt in. This causes a lot of overhead and manually executed mechanical changes across packages. I always wondered if Debian/Ubuntu could benefit from a "monorepo". It seems to work for other distributions, e.g. A…
I don't think it necessarily needs a monorepo, but having every package on Salsa (Debian's GitLab installation) would help.
juat for this comment this account
password is cator
but they needed 8 lettera so I added a F U C K at the tail Like country Joe at Woodstock live added It on the Head with trhee hundred thousans you fuckers out there eehhha! woodstock!!!
whatever
forgot what I was going to say againnn
thata rhw problem with explanatioua offtopics going
and with iphone fckn5 fckn typing shit (sont call it a aystem nor a keyboard fuck)
anaway... id is a public open aource repo or repos or whatever you put it all in neaby place for easiness and selfcompletion righ
but a private business is fucked anyway, even separaring all in diferent repos like the ancient naval fighting weapon named greek fire
anyfuckingway they see everyfuckingahit and anyshit ans anyfuckingthing you fucking programm
my friend
So
qhats the fuxking point of givimg fuxking free away fucking texhnology ???
if you know what I fucking mean righ...
thanks
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…
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 tell, packaging for Arch is straightforward as well.
Earlier quoted context omitted.
That falsely presupposes that only people with poor quality bug reports would be put off from reporting bugs due to the interface. I've known people who can provide high quality, detailed bugs, decide not to because the extra hassles in reporting to Debian just aren't worth it to them.
No, it assumes that quality ratio varies by reporting mechanism. 9 good reports and 1 bad report are better than 18 good reports and 82 bad reports.
You might have a massive problem with a default option, but it's not reported because the people savvy enough to handle the bug reporting can fix it themselves. But that might mean most people using your software are getting a bad impression and most ordinary users are put off.
Depends on whether you're trying to create an elitist grouping or create something to fill people's needs.
It's an interesting, though not unexpected, position that demonstrates technocratic societies can have the same problems of control of power that capitalist societies have; except instead of the elite controlling access to money resources, they control access to technological abilities: "fix it yourself" might be the parallel to saying to a homeless person "get a job".
It's an interesting revelation to me of how a meritocratic society can fail to be egalitarian.