| 1 |
On Fri, 13 Sep 2019 19:44:55 -0400 |
| 2 |
Michael Orlitzky <mjo@g.o> wrote: |
| 3 |
|
| 4 |
> They silently get something less than |
| 5 |
> they're expecting. We would be better off telling people to run "go |
| 6 |
> whatever" themselves, or by putting this stuff in an overlay where |
| 7 |
> expectations are clearly defined. |
| 8 |
|
| 9 |
That suggestion actually decreases security. |
| 10 |
|
| 11 |
Especially if the package in question is intended to be run as root. |
| 12 |
|
| 13 |
At least with using portage, you can side-step the nonsense of "and |
| 14 |
here's how you install this in /usr/bin .... curl url | sudo bash - " |
| 15 |
|
| 16 |
And additionally, we get a sandbox and all the features of file |
| 17 |
ownership tracking. |
| 18 |
|
| 19 |
And if there is a complaint about the package misbehaving, a bug can be |
| 20 |
filed in a common location, and a gentoo dev can actually fix the |
| 21 |
problem, even if upstream have moved on to greener pastures. ( This is |
| 22 |
the sad state of a lot of older perl stuff these days, they simply |
| 23 |
don't work vanilla any more, and gentoo are putting the patches in to |
| 24 |
keep it working ) |
| 25 |
|
| 26 |
So in summary, Portage does a lot more for the end user than "ensure |
| 27 |
dynamic linking works". |
Archives