All Projects

Develop GNU/HyperBK patchset for toolchain (Glibc, Binutils and GCC) and packages.

PATCHING NOTE

Make sure the definitions are not simply duplicated from GNU/Linux' because that will eventually result in
out-of-sync definitions that break for us.

Example of triplet check:	linux*-gnu | gnu* | hyperbk-gnu)
Example of uname check:		Linux|GNU|GNU/*)
Example of C macro check:	defined(__linux__) || defined(__GNU__) || defined(__GLIBC__)
				[note: GNU/Hurd defines __GNU__, and GNU/HyperBK define __GLIBC__ as hardcoded macro]
Example of makefile check:	ifneq (, $(filter Linux GNU GNU_%, $(shell uname -s)))
				[note1: findstring matches subwords, use filter instead]
				[note2: list must be the first parameter, otherwise matching fails]
				[note3: "%" is make's wildcard]

Description:
Historically, Swiftweasel was a Firefox-based application built on XUL platform around 2007 and abandoned in 2010. It was optimized for several architectures using the following methods such as the Profile-Guided Optimization (PGO) and binary code optimization for computers with limited resources.

Since there are users encouraging us develop a Palemoon-based application , and Swiftweasel contains non-trademarked graphics and logos, we could port Swiftweasel to UXP platform as theme for Iceweasel-UXP.

Description:
Historically, Swiftdove was a Thunderbird-based application built on XUL platform around 2007 and abandoned in 2010. It was optimized for several architectures using the following methods such as the Profile-Guided Optimization (PGO) and binary code optimization for computers with limited resources.

Since FossaMail may potentially be revived on UXP in the future [0] and Swiftdove contains non-trademarked graphics and logos, we could port Swiftdove to UXP platform as theme for Icedove-UXP.

Description:
Historically, Icedove was a re-branding of Mozilla Thunderbird by the Debian project, with minimal modifications, in order to resolve branding disputes. Debian since discontinued Icedove after reaching an agreement with Mozilla over the use of it’s trademark.

Otherwise, new Thunderbird will use Quantum, a platform that contains numerous privacy, freedom, and trademark issues, in addition to an ever expanding Google Chromium code base which breaks compatibility with previous versions. Therefore, i suggest port our current Icedove from the deprecated XUL platform to UXP one like our Iceweasel-UXP.

TODO list:

• Remove SSL Error Reporting telemetry from installer/package-manifest.in. [0]

• Add missing emoji browser/fonts/”TwemojiMozilla.ttf” library to UXP sources

• Change Icedove-UXP logo typeface from the non-free “Libertad Book” to free “DejaVU Sans”.

• Rename Icedove to Icedove-UXP in logo typeface.

• Check “Thunderbird” remaining references.

• Fix/adapt confvars.sh to UXP-based applications. (eg. MOZ_APP_VERSION=52.9.`date –utc ‘+%Y%m%d’`)

Description:
Historically, Iceape was a re-branding of Seamonkey by the Debian project, with minimal modifications, in order to resolve branding disputes.

As of December 2013 , Iceape was no longer being maintained by the Debian project and users were encouraged to migrate to other alternatives for security patches.

However, since Seamonkey is being maintained from Thunderbird source and Hyperbola is porting Icedove to UXP platform , it could be built on the UXP platform which contains multiple security and privacy improvements.

TODO list:

• Change Iceape-UXP logo typeface from the non-free “Libertad Book” to free “DejaVU Sans”.

• Rename Iceape to Iceape-UXP in logo typeface.

• Check “Seamonkey” remaining references.

• Fix/adapt confvars.sh to UXP-based applications. (eg. MOZ_APP_VERSION=52.9.`date –utc ‘+%Y%m%d’`)

The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .

Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.

For the future of free computing, we need support architectures that do not come with such malware pre-installed, and the Power9-based Talos II promises to be a great architecture example for workstations and servers environments where Hyperbola is focused since is a fully free long-term support distribution.

Devices like this are the future of computing that Respects Your Freedom and for that reason it’s a high priority for Hyperbola port all packages for the POWER architecture (power64le).

NOTE: POWER porting is focused only for Hyperbola GNU/Linux-libre .

The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .

Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.

For the future of free computing, we need support architectures that do not come with such malware pre-installed, and RISC-V promises to be a great architecture example for low-power computers, laptops and embedded systems, also as ARM architecture replacement.

Devices like this are the future of computing that Respects Your Freedom and for that reason it’s a high priority for Hyperbola port all packages for the RISC-V architecture (riscv64) with multilib support.

NOTE: RISC-V porting is focused only for Hyperbola GNU/Linux-libre .

Seems deleted items reappearing in the Hyperbola feeds since it gives its feed items empty ID string.

Add Hyperbola branding to HyperTask such as HyperWiki and HyperForum for prolixity reasons.

This package contains vague terminology “Open Source”:

core/openssl 1.1.0.e-1
    The Open Source toolkit for Secure Sockets Layer and Transport Layer Security

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

The Free Software toolkit for Secure Sockets Layer and Transport Layer Security

no task description

no task description

This package contains vague terminology “Open Source”:

extra/openjpeg 1.5.2-1
    An open source JPEG 2000 codec

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software JPEG 2000 codec

This package contains vague terminology “Open Source”:

extra/openssl-1.0 1.0.2.k-3
    The Open Source toolkit for Secure Sockets Layer and Transport Layer Security

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

The Free Software toolkit for Secure Sockets Layer and Transport Layer Security

no task description

no task description

no task description

no task description

no task description

no task description

no task description

no task description

no task description

no task description