Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Why does Artix have its own repos (and Arch repos are now disabled by default)?  (Read 1238 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Why does Artix have its own repos (and Arch repos are now disabled by default)?

The way I understand Artix, it is Arch but with some changes - mainly without SystemD.

So I get the reason why Artix needs to patch upstream packages that say, require SystemD or Pulseaudio. But apart from those packages, shouldn't Artix just have the Arch repos enabled (as a default) so that all other packages that don't need such patching be available to download?

Case in Point - I can install Firefox from the Arch repos on Artix (runit) and it runs fine (at least it seems to). Why then is there a Firefox in the Artix repos?

Re: Why does Artix have its own repos (and Arch repos are now disabled by default)?

Reply #1 –
Quote from: sayan – on
Case in Point - I can install Firefox from the Arch repos on Artix (runit) and it runs fine (at least it seems to). Why then is there a Firefox in the Artix repos?
We had this discussion yesterday in #artix-dev. We have 100% of [system] in [core], 85% of [extra] in [world] and almost 35% of [community] in [galaxy], plus additional packages in [universe] and [omniverse] thanks to the tireless efforts of individual developers and packagers.
Now, unless some program hard-depends on systemd-as-pid1, it'll (or should) run fine on Artix. Concerning firefox, the tipping point was the ffmpeg update, which firefox depends on. All our own repo packages are patched and compiled with ffmpeg5, while Arch still has it in staging and firefox is a very popular piece of software to leave it half-broken and unable to play video.
Our build server, thanks to our generous sponsor in Hamburg, is beefy enough to handle the additional workload for the time being. So, the real answer to your question is: because it's popular and because we can afford it.

Re: Why does Artix have its own repos (and Arch repos are now disabled by default)?

Reply #2 –
I read this recently:
https://www.phoronix.com/scan.php?page=news_item&px=Arch-Toolchain-Falling-Behind
These were a couple of comments on that article:
"A perfect opportunity for Manjaro or any downstream distro to step up and give back something of value to the whole stack/team instead of just virusing the c**p out of Arch upstream work and make money with it. "
"Manjaro can help. It would be good if two communities could united together or help each other in a feasible way."
"If by "help" you mean "wait until 2-3 weeks after Arch has done the work, then DDOS part of the Arch infra" then yes, they can help. "

It's probably more polite and considerate towards Arch if there are separate Artix repos as it grows in popularity, if it's possible to do so.

Those are smart kids in that link, if they are building all the Artix packages.  ;D  Very kind of them! Thank you indeed.

Re: Why does Artix have its own repos (and Arch repos are now disabled by default)?

Reply #3 –
Quote from: ####### – on


It's probably more polite and considerate towards Arch if there are separate Artix repos as it grows in popularity, if it's possible to do so.


Slightly beyond scope of the thread, yes, we don't use any arch binary packages, ie we don't use arch mirrors to build our repos.
Artix runs with artix repos only, to include arch epos is purely optional and user choice.
What we do use from arch is their PKGBUILDs, if necessary tweaked of course, so we only pull from their github mirror the tree.
In a sense, arch maintains a good chunk of the PKGBUILDs, which we complement with non systemd ones, but all packages are built by artix.