Skip to main content
Topic: Packagers wanted! (Read 6143 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

Re: Packagers wanted!

Reply #30
I want tto start by making a package for VIM.  Would that be an acceptable place to start?  I'm not happy with the ones that are produced and I think I can do better on a private compile.  But setting it up into a pacman package makes more sense and I can learn about pacman and PKGBUILDER then

Re: Packagers wanted!

Reply #31
I want tto start by making a package for VIM.  Would that be an acceptable place to start?  I'm not happy with the ones that are produced and I think I can do better on a private compile.  But setting it up into a pacman package makes more sense and I can learn about pacman and PKGBUILDER then
We are not looking to change packages from upstream arch. The only changes that should be made is to remove systemd where necesarry. No other changes will be accepted for vim or any of the other upstream packages from arch without a good reason. You are welcome to publish and share special vim builds in your own unofficial repos, but they will not be allowed under Artix official repos. The reason is that we import packages from arch constantly, and the idea is to follow arch's packages, and if people start changing packages to be too different from Arch it makes importing more difficult and more likely to have errors and problems. Also remember that a distro is designed with other people in mind, just because you don't like how a package is done doesn't mean that others do not like it. The packages are designed in a way that the majority of users will like and use, and for the small number of people who don't like it would rebuild it for their peraonal machines.

Packaging for Artix entails 2 possible forms.
1) If it is an upstream package that is in arch, you may not modify it except where necessary to remove systemd or to make it work on non systemd systems.
2) If it is a package that does not exist in Arch you are free to do what you want with the PKGBUILD of your package, but only your package, you cannot modify somebody else's package without their permision. As example, I maintain the pamac and pamac-classic packages for Artix. They are not in Arch Linux which means that I choose how the PKGBUILD is done, and if anybody else wants to modify it, they would have to ask my permission first.

Hopefully this info helps understand a bit more what packaging under Artix is like.
Chris Cromer

Re: Packagers wanted!

Reply #32
Thanks.

It is too bad though because it seems like packages from Arch seem to be the ones that are the most broken, and this repeatedly ends up being the case.  I thought that once we get to a completed core non-systemd os working, that we would start to become more independent on arch.

In order to make a contribution then, we really need to be experts on systemd and the free desktop components, in order to seperate them out and handle substitions for udev etc.  That is a long term problem.  It puts the development in a situation where it always has to follow changes in someone elses technology and to adapt to it, when the people you are adapting from are openly hostile to your effort.

If it is possible, can we get a list of packages that need conversion  and that artix is looking to modify?

Re: Packagers wanted!

Reply #33
Hanging on guys and I'll give all the help I can.  Got to go do a rehab thing first though.  Be about 6 months,  and heroin free me for packaging and programming lol

Re: Packagers wanted!

Reply #34
Do you have a list of what packages are needed most?

Re: Packagers wanted!

Reply #35
Do you have a list of what packages are needed most?

Not particularly. You can start with the ones you use yourself or those occasionally requested here in the forum. Contaminated packages are preferred.

 If you feel serious about it, join freenode/#artix and ask for an invite to the dev channel.

Please, have a look at our documentation.