-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvoid-packages:issues:2387.html
40 lines (40 loc) · 2.03 KB
/
void-packages:issues:2387.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="utf-8" />
<title>Re: [voidlinux/void-packages] Package request: palemoon (#2387)</title>
<style>section{white-space:pre-wrap;}</style>
</head>
<body>
<main>
<h1>Re: [voidlinux/void-packages] Package request: palemoon (#2387)</h1>
<section id="post1">
<h5>crocket at <a href="#post1">Sat, 10 Feb 2018 00:17:33 +0000 (UTC)</a></h5>
one browser? Do you mean palemoon and basilisk?
</section><section id="post2">
<h5>Enno Boland at <a href="#post2">Mon, 23 Apr 2018 23:04:00 -0700</a></h5>
Nope, not in the mood to get threats..
</section><section id="post3">
<h5>Enno Boland at <a href="#post3">Tue, 24 Apr 2018 06:04:01 +0000 (UTC)</a></h5>
Closed #2387.
</section><section id="post4">
<h5>Jakub Skrzypnik at <a href="#post4">Mon, 23 Apr 2018 23:25:04 -0700</a></h5>
Just for reference, can I get a backstory about that? :)
</section><section id="post5">
<h5>crocket at <a href="#post5">Mon, 23 Apr 2018 23:26:48 -0700</a></h5>
palemoon developers refused to support musl, so void-packages maintainers refused to include palemoon, too.
</section><section id="post6">
<h5>Helmut Pozimski at <a href="#post6">Mon, 23 Apr 2018 23:42:43 -0700</a></h5>
They also refuse to support current gcc versions which makes it unfit to be included in a rolling release distribution.
</section><section id="post7">
<h5>Enno Boland at <a href="#post7">Mon, 23 Apr 2018 23:55:08 -0700</a></h5>
For reference: https://github.com/jasperla/openbsd-wip/issues/86
</section><section id="post8">
<h5>Enno Boland at <a href="#post8">Tue, 24 Apr 2018 00:06:36 -0700</a></h5>
Void packages lots of stuff that refuses to support musl ( == proper standards).
In contrast to openbsd-wip, which only distributes build instructions, (this is why the linked issue isn't reasonable) we ship binaries. That means the threats that were done to the linked repository actually apply to Void if we would add palemoon with system libraries.
</section>
</main>
<nav><a href="index.html">Issues list</a></nav>
</body>
</html>