News for hackers. Stuff that matters.
Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @09:55AM (#17799868)
Packaging was a solved issue in Linux, congrats on the 3 steps back.

The rush towards containers because they're "easy" strikes yet again.

My fear is that the handful of companies that build packages for their desktop apps with abandon them and move to Flatpak/Snap. From the Flatpak docs it looks like anyone and everyone can just get access, even if you don't own the thing you're packaging. So if you pack $newpopularsoftware first you can now install malware on everyone's computers with a single push.

It's like they looked at everything bad about Chocolatey/NPM/pip/AUR and just ran with it.

Re:Flatpak 1.0 Released, Ready for Prime Time by nickik on Monday August 20, 2018 @10:27AM (#17800157)
> Packaging was a solved issue in Linux

That's an insane thing to say. Literally 100s of people doing the same thing adding no value to the end user. That is a waste amount of resources waste by the open source community.

> My fear is that the handful of companies that build packages for their desktop apps with abandon them and move to Flatpak/Snap.

Good? Why does it matter to you.

> From the Flatpak docs it looks like anyone and everyone can just get access, even if you don't own the thing you're packaging. So if you pack $newpopularsoftware first you can now install malware on everyone's computers with a single push.

Nothing stops you or any distribution from having a repo with reviewed or specially selected software.

Also, the waste majority of packagers would not have found that malware anyway.

Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @11:22AM (#17800697)
> That's an insane thing to say. Literally 100s of people doing the same thing adding no value to the end user. That is a waste amount of resources waste by the open source community.

Or you know developers could package their own software. It's some upfront effort but usually set and forget. Things like FPM[1] make this even easier. Personally I don't know why developers find packaging so hard, I've had to package hundreds of bit of software for different distros (and versions of said distro) over my career and it's usually set and forget with some changes when there are big underlying changes to the OS like sysv > systemd. Granted my experience is with non GUI apps so I can imagine there is likely some pain points between different distros/version when it comes to the hot mess that is DEs.

> Good? Why does it matter to you.

Because I have to go from trusting 1 vendor to install 1 package (and dependencies) to 1 3rd party repo that anyone can push to. That is a huge change in the trust model.

> Nothing stops you or any distribution from having a repo with reviewed or specially selected software.

We already have those.

> Also, the waste majority of packagers would not have found that malware anyway.

This isn't about trusting the software in the package it's about trusting the package maintainer, who could now be absolutely anyone with no verification or validation. See malware in other user run repos like NPM, pip, AUR etc...

1. https://github.com/jordansissel/fpm

Re:Flatpak 1.0 Released, Ready for Prime Time by jamesgeck0 on Monday August 20, 2018 @01:49PM (#17802071)
> Or you know developers could package their own software.

When I was a Linux user, I've seen so many packages that worked on one Debian derivative but had problems on another. Maybe this is a solved problem now? It definitely wasn't solved from a user perspective five years ago.

Re:Flatpak 1.0 Released, Ready for Prime Time by nickik on Monday August 20, 2018 @01:12PM (#17801723)
> Or you know developers could package their own software.

As a developer I can tell you right now that I'm not gone package everything for for 100s of linux distros that I don't even know the name of.

> It's some upfront effort but usually set and forget. Things like FPM[1] make this even easier. Personally I don't know why developers find packaging so hard, I've had to package hundreds of bit of software for different distros (and versions of said distro) over my career and it's usually set and forget with some changes when there are big underlying changes to the OS like sysv > systemd. Granted my experience is with non GUI apps so I can imagine there is likely some pain points between different distros/version when it comes to the hot mess that is DEs.

Have you ever thought about maybe that doing something a lot makes you good at it.

Many developers are not linux expert, and don't know the many difference between the distros and the package managers, or even the different distros using the same manager.

Saying its 'fire and ferget' when there are so many distors who are all moving targets with different targets, release cycles and so on, its just basically lying.

But that's not all, you also have to get bug reports from many different people that you can not reproduce.

> Because I have to go from trusting 1 vendor to install 1 package (and dependencies) to 1 3rd party repo that anyone can push to. That is a huge change in the trust model.

So the fact that some poor debian maintainer had to wrap the venders app with some debian specific glue makes it safer?

If you don't trust the vender of your software, you can trust that they maintain a repo where you can download it. That might be Flathub for some smaller once, but others will have their own.

There is not more trust involved at all, maybe you move trust from Debian to Flathub, but that's it.

> We already have those.

Not with the advantages of the maintainer only having to publish one software package.

> This isn't about trusting the software in the package it's about trusting the package maintainer, who could now be absolutely anyone with no verification or validation. See malware in other user run repos like NPM, pip, AUR etc...

It is already absolutely anybody. Do you know all the people who package for Debian?

Also, if don't want to use apps directly from Flathub, you don't have to. You can only use software that has been validated by the Flathub community, or when somebody like Fedora uses the app.

Forcing 1000s of man hours of voluntary work just so you can claim "Some guy lightly related to the X distro project has taken a couple hours to see if it doesn't crash" so that's what I'm gone base my security on is a insane approach.

That's a terrible, terrible security architecture and the only reason anybody is defending it is because that's who it used to be and that somehow makes it good.

Re:Flatpak 1.0 Released, Ready for Prime Time by scrollaway on Monday August 20, 2018 @10:06AM (#17799961)
> Packaging was a solved issue in Linux, congrats on the 3 steps back.

Dude, seriously. Flatpak has issues, but saying "Packaging was a solved issue" when every distro rolls out its own packaging system is the reason we can't have nice things.

Ignoring the problems won't make them go away.

Re:Flatpak 1.0 Released, Ready for Prime Time by dec0dedab0de on Monday August 20, 2018 @10:15AM (#17800036)
Dude, seriously. Flatpak has issues, but saying "Packaging was a solved issue" when every distro rolls out its own packaging system is the reason we can't have nice things.

If every distribution was using the same packaging system, would they still be separate distributions?

EDIT: By packaging system I assumed we meant the same repositories, and packages. Since that is how Flatpak seems to work.

Re:Flatpak 1.0 Released, Ready for Prime Time by oblio on Monday August 20, 2018 @10:36AM (#17800230)
> If every distribution was using the same packaging system, would they still be separate distributions?

Do we even need that many distributions? What's the value proposition for all those hundreds of Linux distros?

My impression is that for many of them its:

A. we want to make my own distro, to learn, get visibility or maybe even make money

B. we want to make our own distro because of an already existing user base from point A.

C. we want to make our own distro because we can't get along with distro X makers

I wish that the barrier to entry to making a Linux distro was higher. People would have to put more thought and effort into it and the overall quality would be higher.

Re:Flatpak 1.0 Released, Ready for Prime Time by dec0dedab0de on Monday August 20, 2018 @10:59AM (#17800470)
Do we even need that many distributions? What's the value proposition for all those hundreds of Linux distros?

That is a valid point, and why I usually tell people to just use Ubuntu if they're not sure. The value proposition is that different people are doing different things, and even people doing the same thing sometimes like to do it different ways.

I wish that the barrier to entry to making a Linux distro was higher. People would have to put more thought and effort into it and the overall quality would be higher.

I believe that less competition equals lower quality.

Re:Flatpak 1.0 Released, Ready for Prime Time by oblio on Monday August 20, 2018 @11:20AM (#17800676)
> I believe that less competition equals lower quality.

While I generally believe in competition leading to better results for users/customers, the real life experience of Linux distros vs Windows or Mac OS doesn't seem to bode well for the free market :p (i.e. Linux distros should be the pinnacle of software quality and they aren't).

Re:Flatpak 1.0 Released, Ready for Prime Time by AnIdiotOnTheNet on Monday August 20, 2018 @10:40AM (#17800270)
D. We want to make our own distro because we finally got this gigantic mess of independently designed and developed software to almost kind of work the way we want it to, and now we have to maintain it that way because it was so much work to get here.
Re:Flatpak 1.0 Released, Ready for Prime Time by detaro on Monday August 20, 2018 @10:21AM (#17800095)
Are Debian and Kubuntu separate distributions?

Would RedHat switching to apt make Debian redundant?

Re:Flatpak 1.0 Released, Ready for Prime Time by jcelerier on Monday August 20, 2018 @04:16PM (#17803535)
> Are Debian and Kubuntu separate distributions?

yes because Debian (stable) and Kubuntu have different KDE packages

> Would RedHat switching to apt make Debian redundant?

- no because they apply different patches - yes because I think that both Debian and Red Hat and any distro which applies patches is already redundant with Arch

Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @05:19PM (#17804075)
You seem to be confusing packages and package managers.
Re:Flatpak 1.0 Released, Ready for Prime Time by TingPing on Monday August 20, 2018 @10:32AM (#17800193)
> EDIT: By packaging system I assumed we meant the same repositories, and packages. Since that is how Flatpak seems to work.

Flatpak is entirely decentralized, anybody can make a custom runtime (Debian/Fedora ones exist), and anybody can host a repository.

Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @11:33AM (#17800782)
How's that different from current package managers?
Re:Flatpak 1.0 Released, Ready for Prime Time by TingPing on Monday August 20, 2018 @04:40PM (#17803747)
Its not, its only different than Snap which is centralized. Their comment implied that Flatpak was too.
Re:Flatpak 1.0 Released, Ready for Prime Time by nickik on Monday August 20, 2018 @10:23AM (#17800116)
yes of course they would. Using the same package manager does absolutely not require the same directory structure.

If they used the same packages, then there would be a question if they are separate distributions.

Re:Flatpak 1.0 Released, Ready for Prime Time by dragonwriter on Monday August 20, 2018 @10:10AM (#17799986)
> every distro rolls out its own packaging system

But, they don't. Lots use Debian’s, for instance.

Re:Flatpak 1.0 Released, Ready for Prime Time by tracker1 on Monday August 20, 2018 @01:49PM (#17802070)
Umn, the software developers for X don't necessarily run the packagins systems for deb, apt, etc. There's nothing stopping RedHat from maintaining their own Flatpak "store", ditto for Ubuntu, etc.

What this does is allow software to keep working when a library update happens without having to spend hours/days tracking down wierd scripts you don't even understand and running them as root to fix your problem. Not everyone wants to write OS-level software or fix every bug themselves.

Hell, my GF watched me install something that wasn't in the UI app center (whatever it is called) via command line, and was like, "WTF do you have to do that? That's the most stupid thing I've ever seen." The fact is, she's not wrong.

Re:Flatpak 1.0 Released, Ready for Prime Time by alkonaut on Monday August 20, 2018 @10:03AM (#17799933)
> if you pack $newpopularsoftware first you can now install malware on everyone's computers with a single push.

How does this compare to the traditional package managers?

Re:Flatpak 1.0 Released, Ready for Prime Time by cpburns2009 on Monday August 20, 2018 @10:19AM (#17800075)
Well, looking at the procedure for Snap [1] there's no review at all. Flatpak [2] defers to Flathub [3] which has some sort of review: a pull request on Github but I'm not sure how thorough that is. Traditional package repositories have a review phase before you can get your package into the system (that's how it is with Debian at least).

[1]: https://docs.snapcraft.io/build-snaps/upload

[2]: http://docs.flatpak.org/en/latest/publishing.html

[3]: https://github.com/flathub/flathub/wiki/App-Submission

Re:Flatpak 1.0 Released, Ready for Prime Time by alkonaut on Monday August 20, 2018 @10:23AM (#17800117)
How does that review work in the case of binary/proprietary packages?
Re:Flatpak 1.0 Released, Ready for Prime Time by TingPing on Monday August 20, 2018 @10:34AM (#17800211)
Flathub reviewer here. We do not security audit code of any project as thats just unreasonable. The user puts ultimate trust in the upstream projects we just ensure that the right upstream is used, libraries are up to date and sanely built, permissions are as reasonable as they can be, etc.

This is identical to every traditional distro like Debian or Fedora.

Re:Flatpak 1.0 Released, Ready for Prime Time by cpburns2009 on Monday August 20, 2018 @10:31AM (#17800181)
I'm assuming you're talking about traditional package managers. Proprietary packages aren't uploaded to the main package repositories from what I've seen. The company will typically provide the packages themselves (e.g., a deb or rpm file), and sometimes they'll provide their own repositories for easier delivery. This has been my experience with Dropbox, SpiderOak, and Sublime Text.
Re:Flatpak 1.0 Released, Ready for Prime Time by alkonaut on Monday August 20, 2018 @10:35AM (#17800221)
Got ya. They create their own repositories, and don't use the central one.
Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @10:41AM (#17800281)
The review is to get your access to publish, not the code submitted. So pass that, package honestly for 6 months, deploy malware.
Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @10:32AM (#17800195)
If I need software not found in my upstream repos you have 3 options:

1. Packaged by the developer/publisher, see Virtualbox, Spotify, Chrome, Slack etc...

2. Packaged by a single 3rd party, see PPAs

3. A central 3rd party repo populated by anyone, NPM, AUR, pip, Snap/Flatpak etc..

Case 1: I have to trust the developer/publisher which is sensible, you're already trusting their code to run.

Case 2: I have to trust some random 3rd party, sometimes this is possible, sometimes not but if I do trust them I'm trusting them for one package (and maybe it's dependencies). I may have multiple options of who to trust to provide this package.

Case 3: Anyone can package anything if they get there first they can publish things however they like. The problem is that they are implicitly trusted by the repo, not me.

The first 2 are acts of active trust, I have to verify the person/company I'm downloading and make a decision whether I trust them or not. With a 3rd party central repo (it doesn't matter what format) I do not have that option, I either trust everything that anyone can publish to be correct or I don't use it.

Re:Flatpak 1.0 Released, Ready for Prime Time by j605 on Monday August 20, 2018 @03:36PM (#17803149)
AUR, snap and flatpak all work differently. AUR is free for all with no trust implied or given but packages will be removed upon user intervention. So curation is basically done by users and other administrations but it doesn't prevent bad packages from being uploaded in the first place. Most of the AUR is building from source so you just have to read the build scripts (PKGBUILDs) of each package before installing and do what a maintainer does.

It gets easier on updates since you only have to check diffs between versions. I believe you are making a wrong decision if you trust anything on the AUR implicitly.

Re:Flatpak 1.0 Released, Ready for Prime Time by deadbunny on Monday August 20, 2018 @05:20PM (#17804094)
> I believe you are making a wrong decision if you trust anything on the AUR implicitly.

That's basically my entire point.

Re:Flatpak 1.0 Released, Ready for Prime Time by digi_owl on Monday August 20, 2018 @01:24PM (#17801842)
> It's like they looked at everything bad about Chocolatey/NPM/pip/AUR and just ran with it.

Basically they did just that. The only "desktop" devs left in Linux land are really cloud devs that dabble in desktop on the side. Damn it, i have been basically told to clam up when i complained about the cloud mentality having no home on the desktop. Because apparently only could mattered because it was the big Linux user case.