Viper (*)

[FabioLolix]

1

Viper Linux (DOA)

• https://www.viperlinux.org/
• https://x.com/viperlinux
• https://github.com/ViperLinux
• https://gitlab.com/ViperLinux

---

2

• Introducing Viper fastfetch-cli/fastfetch#2069
• https://github.com/cppdark96/Viper

---

3

From memory there was also a short lived Fedora derivate (update, it was Viperr)

[cppdark96]

Well now is not empty anymore, and also there is a difference, my distro I just called it "Viper", but the other project is called, "Viper Linux", so I'm not including the word "Linux" on it. And also since I added and adapted first the name and the logo to the fastfetch code and made the PR, it would be fair if I get the chance in this instance.

My current Archiso-LIVE-ISO folder for Viper:
https://github.com/cppdark96/Viper

Also here is my gitlab with all the code that I created for viper:

https://gitlab.com/users/cppdark96/groups

It is very organized into 4 groups:

• repos
• calamares
• viper-system-components
• viper

And also there is the beta ISO for my current distro in sourceforge:
https://sourceforge.net/projects/viper/files/viper-beta-iso/

[FabioLolix]

Well now is not empty anymore

Ok

also there is a difference, my distro I just called it "Viper", but the other project is called, "Viper Linux"

That's why the issue is called Viper (*) instead of Viper

Also here is my gitlab with all the code that I created for viper:

Thanks

---

I've took a look at your package repository:

• packager field is not set in your makepkg.conf (packager = Unknown Packager from .BUILDINFO)
• packages are 'dirty builded' with makepkg (you have installed q4wine-git, python2 and I'm pretty sure your DE is xfce)
• 3 python2- packages are present (cairo,gobject,numpy) but not python2
• there are at least 3 programs that prohibit redistribution (visual-studio-code-bin, sublimetext and jetbrains-toolbox)
• also I get this is a new project and pkgs are commited to the git repo but they are not signed

[cppdark96]

I've took a look at your package repository:

packager field is not set in your makepkg.conf (packager = Unknown Packager from .BUILDINFO)
packages are 'dirty builded' with makepkg (you have installed q4wine-git, python2 and I'm pretty sure your DE is xfce)
3 python2- packages are present (cairo,gobject,numpy) but not python2
there are at least 3 programs that prohibit redistribution (visual-studio-code-bin, sublimetext and jetbrains-toolbox)
also I get this is a new project and pkgs are commited to the git repo but they are not signed

Yeah but remember it is a W.I.P project, and I'm aware of those things, about the packager not really an issue, I have experinece working on Arch distros and that is definitely something that is not that relevant.

Even though python2 is not present at the moment, because compiling that takes too long and I have no infinite time then that's something for later but yeah of course I know that I have to put it also in the extra repo.

About programs that are prohibited for redistribution, there isn't any of those packages present in the packages.x86_64, so I'm not redistributing them illegally, now the fact that I have those packages present in my "viper-extra" repo, doesn't mean I'm redistributing them illegally, find me one serious Arch distro, that doesn't have those key packages in their repos, also find me someone who is in a real legal trouble because of something like that, so if you excuse me that is just silly to use that as a reason to put my project down.

Packages not signed? I'll sign them later if I want, may be I want to do it may be I don't again I have a normal life a gf a job, I'm not gonna be pulling my hair and deliberately waste time, just because the W.I.P distro is not perfect yet, things take time and I'm not force to please anybody or seek aprobal from nobody just because you're against of me using a specific name, honestly I don't care.

[FabioLolix]

Yeah but remember it is a W.I.P project

As said in my post above also I get this is a new project [...]

just because you're against of me using a specific name

I'm not against you using Viper as name, also no one care about Viper Linux that have an empty website, empty twitter account and empty github/gitlab, coincidentially I found it after your PR on fastfetch and was mentioned here for the records

so if you excuse me that is just silly to use that as a reason to put my project down.

Mine were observation not a conviction

[cppdark96]

Mine were observation not a conviction

All right, quite an observation sure, but what would you propose to solve the issue? Considering the other Viper distros are not even active.. is worth it to take a look at them even?