Redcore Linux Project Forum

It will work, but it may take a long time to recompile everything affected by the USE changes. It's just easier to install Redcore, remove sisyphus and use the system  as you would use Gentoo. Redcore is basically Gentoo with binary packages, and sisyphus to deal with those binary packages. But you can absolutely remove sisyphus  and use emerge.

sisyphus install zfs

Will pull everything needed for zfs to work, including zfs-dkms. zfs-kmod is a Gentoo ebuild, and not recommended or compatible with Redcore. zfs-dkms on the other hand works with Redcore kernels. After install, you will need to reboot, and dkms will build the kernel modules.

If you encounter an error, please let me know.

Well, when I designed sisyphus, I considered someone might want to override some defaults. In fact, I was hoping someone will eventually ask me this question. So, you don't really need to branch out. Sisyphus has a mechanism to override the defaults. Not everything in your list is possible, but 3 out of 4 are.

1. Edit /etc/portage/env/10-sisyphus-overrides and add the following lines :

CFLAGS="-O2 -march=native -mtune=generic -pipe -fno-delete-null-pointer-checks -Wno-deprecated -Wno-deprecated-declarations -fno-plt -fstack-protector-strong -fstack-clash-protection -fcf-protection=full"
CXXFLAGS="-O2 -march=native -mtune=generic -pipe -fno-delete-null-pointer-checks -Wno-deprecated -Wno-deprecated-declarations -fno-plt -fstack-protector-strong -fstack-clash-protection -fcf-protection=full"

Feel free to edit these flags however you please. The only change from Redcore's default is -march=native instead of -march=x86-64

Then, let's say you want to compile GCC with -march=native :

Edit /etc/portage/package.env/10-sisyphus-overrides and add the following line :

sys-devel/gcc 10-sisyphus-overrides

For every package you want to compile with -march=native you add another line :

category/name 10-sisyphus-overrides

2. Edit /etc/portage/package.use/10-sisyphus-overrides and add the following line :

sys-devel/gcc graphite

For every package you want to change an USE flag you add another line:

category/name USE

to enable an USE flag or

category/name -USE

to disable it

3. https://bugs.gentoo.org/715612 , this one is a work in progress, once it shows up in Gentoo's tree, you can follow the steps I described at number 2 to enable it.
4. Follow the steps at number 2 and add the following line:

app-alternatives/bzip2 -reference lbzip2

This will change the bzip2 implementation from reference (default implementation) to https://github.com/kjn/lbzip2/

or

app-alternatives/bzip2 -reference pbzip2

This will change the bzip2 implementation from reference (default implementation) to https://launchpad.net/pbzip2

Once done, the changes are permanent and sisyphus will NOT use binaries for the packages altered this way. All you have to do is run

sisyphus upgrade --ebuild

and you will notice it will offer to recompile the altered packages with your settings. If anything goes wrong, just remove the alterations and re-run

sisyphus upgrade --ebuild

Sisyphus has a fallback mechanism, so the --ebuild flag becomes automatically redundant and will use binaries if alterations are removed.

P.S.: There is no global override, changes are possible only per-package basis. Recompiling the whole system with -march=native is possible using a global override, but it is not implemented yet.

gpasswd -a your_username deluge

Followed by a logout-login cycle *should* sort it.

I don't expect any impact on Redcore Linux.

I am happy they provide binary packages. If they did this 10 years ago, Redcore Linux wouldn't have existed, probably. For the past 10 years, we've been producing our binaries in the same way as they do in their shiny new repository.

I started Redcore Linux to make Gentoo Linux more accessible. I like to think that maybe Redcore Linux somehow influenced Gentoo Linux's decision to provide binary packages, finally.

That being said, Sisyphus will NOT be using their binary packages. Their's use the newer package format, while we use the older package format. They can use ours, thanks to backwards compatibility, we cannot use theirs, for the time being.

A migration to the newer package format is in the cards for Redcore Linux, but it will be some months away, as everything will have to be rebuilt. Not a major issue, we tend to rebuild every single package once a year anyway, the next mass rebuild will probably come with a format change as well.

The format change will potentially make the binaries of both distros interchangeable, however, at least for the time being, Gentoo Linux doesn't seem to provide binaries for the testing branch, on which Redcore Linux is based. Which means, that even with identical package formats, Redcore Linux will carry on using its own binary packages, aka business as usual.

I updated the wiki before actually merging the packages. I merged them now. Try in a couple of hours so they have time to sync to the mirrors and it should work. If not, let me know.

You need to follow those steps exactly and it should work.

No worries, if you keep having issues, let me know.

That means the system is not fully upgraded, and your latest attempt failed somehow. Try this :

emerge --sync
cd /opt/redcore-build
git fetch --unshallow
git fetch --all
git reset --hard 5361e6b8970e53046955ac5071d9122990cf77ec
emerge -va1 sisyphus sisyphus-qt
sisyphus branch master
sisyphus rescue
sisyphus upgrade

This should work. If you have issues, please let me know.

Yes, this is the correct solution.

GRUB_THEME="/usr/share/grub/themes/redcore/theme.txt"

Comment the above line in /etc/default/grub and run :

grub2-mkconfig -o /boot/grub/grub.cfg

Sisyphus already tells you what's wrong. Somehow you deleted the package cache directory. Just recreate it :

mkdir -p /var/cache/packages