We urgently need more people able to contribute to packaging.
You don't have to be an expert in the occult arts for that; an elementary grasp of Linux in general and how PKGBUILD works should be enough for basic contributions. Help and training will be provided, free of charge!
You can apply here or in PM.
[EDIT/UPDATE]
Artix has moved to Libera network: irc.libera.chat -- TLS/SSL ports 6697, 7000 and 7070.
Potential packagers should use an IRC client (https://libera.chat/guides/clients) to connect to liberachat (https://libera.chat/guides/connect), register a nickname (https://libera.chat/guides/registration) and join #artix. Ask for an invite to #artix-dev stating your intent and eventually a staffer will invite you (we're always busy with real life and located across a large span of time zones, please be patient).
Once invited, you'll be asked questions by the Spanish Inquisition team about your skills and abilities. To ensure our team's integrity and the safety of our user base, we are somewhat picky on our standards, please expect some delay before access is granted (if at all) to new team members.
Count me in
Guess I'll never know if I don't try, PM me and we can look for a date for me to frustrate you :P
My time is pretty limited, but I might be able to help some. I used to maintain several of the orphaned OCaml libraries in Arch so I have some experience with PKGBUILD. What is involved?
I may be able to help, let me know.
Yup, I'd like to help with that as well!
Hey man I just made my first 3 PKGBUILD's, I made them out of git repos instead of them being like actual packages with version numbers/etc, all I really need to learn is how to give it a version number & how to make it automate its own updates...
like... when there's a new package available to be packaged, how do we know? Do the packages just update themselves or do we need to alter the PKGBUILD to make it update in the package manager? I can start with gaming emulators, I have so far done Dolphin-emu, Citra-emu & Medusa-emu, once I am more experienced I'll be able to do other packages. Maybe in a few months I'll have enough experience to do more packages but I would prefer to start with stuff that requires cmake, qmake or ./configure
Inbox me if you don't mind & just teach me a few of the things I have mentioned here that I don't understand & I'll be good-to-go for the simple packages, and you guys can look over the first ones I make to make sure I am doing everything right & give me tips about what I am doing wrong. This is the first one I made, I made a similar one for citra-emu & medusa-emu.
pkgname=dolphin-emu-fresh
pkgver=0
pkgrel=1
pkgdesc='A GameCube / Wii / Triforce emulator'
arch=('x86_64')
url='http://www.dolphin-emu.org/'
license=('GPL')
depends=('alsa-lib' 'bluez-libs' 'cairo' 'enet' 'gcc-libs' 'gdk-pixbuf2'
'glib2' 'glibc' 'gtk2' 'hidapi' 'libevdev' 'libgl' 'libpng' 'libpulse'
'libsm' 'libx11' 'libxi' 'libxrandr' 'libxxf86vm' 'lzo' 'mbedtls'
'miniupnpc' 'pango' 'sfml' 'zlib' 'pulseaudio' 'ffmpeg' 'pugixml'
'bluez' 'bluez-utils-compat' 'bluez-firmware' 'bluez-plugins'
'bluez-libs' 'bluez-qt' 'bluez-tools' 'bluez-openrc' 'curl' 'xorg-xinput'
'libeudev' 'libusb' 'libgusb' 'libusb-compat' 'lib32-libusb' 'libtiger'
'pangomm' 'pangox-compat' 'libglvnd' 'sndio' 'alsa-plugins' 'alsa-firmware'
'alsa-utils' 'alsa-lib' 'pulseaudio-alsa' 'alsa-oss')
makedepends=('cmake' 'git' 'qt5-base' 'pango' 'fakeroot')
source=('dolphin-emu::git+https://github.com/dolphin-emu/dolphin.git')
sha256sums=('SKIP')
build() {
git clone https://github.com/dolphin-emu/dolphin.git
mkdir -p dolphin/build
cd dolphin/build
cmake -DOpenGL_GL_PREFERENCE=GLVND -DUSE_X11=1 -DUSE_EGL=1 -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_QT2=TRUE -DCMAKE_BUILD_TYPE=Release ..
make -j48
}
package() {
cd dolphin/build
make DESTDIR="${pkgdir}" install
install -Dm 644 ../Data/51-usb-device.rules -t "${pkgdir}"/usr/lib/udev/rules.d/
}
# make install
# install -Dm 644 ../Data/51-usb-device.rules -t "${pkgdir}"/usr/lib/udev/rules.d/
# vim: ts=2 sw=2 et:
@kenny_w Be aware that git packages belong to AUR only and should have "-git" suffix in the package name.
these git packages are mostly used to test new features...
"-git" pgkbuilds are updated only when there is something wrong with current pkgbuild or when there was change in buildsystem...
these pkgbuilds can stay unchanged for years and when building always offer newest version.
git pkgbuilds usually have "version" function, so when you build them the version is set to current one.
Normal PKGBUILDS used in our repositories are downloading specific version of desired program,
PKGBUILD is updated when the new release is made or when there is some error with pkgbuild.
PKGBUILD which you posted is mixture of these, it is good for personal use but nightmare for others.
- downloads source from git (build is not stable, you cant offer stable package)
- Package name should reflect that the source is from git with "-git" suffix
- Package version should specify program version (in case of "-git" package provide "version" function)
- Make things easy to read (dont mix tabs and spaces, indent body of functions)
- Long lines are hard to read, if you can cut long line to multiple short lines
These are my thoughts regarding this subject, i might also be totally wrong :D.
@nous I may be able to help some let me know what you need
Do you need extra package maintainers or not? I'd be happy to help.
Not much free time, nor an expert but would like helping in this regard.
I could help as well.
I would like to be of service.
Quite busy all the time, but I'll give my best.
I have unexpected free time and can give it maybe about 2 hours a day. I have no idea where to really start.
You can read the online documentation (https://github.com/artix-linux/documentation/blob/master/Notes%20for%20packagers.markdown).
OK - I'm reading.
I'm willing to help and to learn.
I've got a bit of experience with building packages for Puppy Linux.
However, I would need a crash course on how to do things properly with PKGBUILD.
PKGBUILDs are just bash scripts, parsed by makepkg. You can read the Arch wiki entries for more information on variables and functions.
A basic how-to pertaining to Artix package operations can be found in our Github documentation page (https://github.com/artix-linux/documentation/blob/master/Notes%20for%20packagers.markdown).
I suggest you create a couple of packages on the AUR so as to familiarize yourself with how package maintainance works; we'll be around for the rest. Cheers!
https://linux.slashdot.org/story/18/07/14/0049259/systemd-free-artix-linux-os-is-looking-for-packagers
Hey... I maintain some AUR packages on Arch.
I admire the Arch build system!
And have much exp. with it as well as Gentoo's portage, will be more than willing to help!
Where can I get information about what exactly needed?
I could also write some article on Wiki about package building scenarios.
(saw the slashdot story)
I would hate for Artix to die simply due to a lack of package maintainers, so I'm willing to help as I can.
I would like to contribute.
I'm in. Checking out https://github.com/artix-linux/documentation/blob/master/Notes%20for%20packagers.markdown
@kninja @squeakypancakes @harshavenu99 For better and faster communication, please join Freenode, register a nick and poke nous, artux, sgorava or artixelf for an invitation to #artix-dev. Any questions, feel free to ask here or by PM.
Cheers!
Free Node is on irc. Use a client like hexchat
/Server #freenode
https://freenode.net/kb/answer/registration
for registering a name.
/join #artix
https://www.reddit.com/r/linux/comments/90xhr4/artix_linux_with_openrc_or_runit_is_looking_for/
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.
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?
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
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 (https://gitea.artixlinux.org/artix/documentation/src/branch/master/Notes%20for%20packagers.markdown).
I think i will soon be ready to create and build packages for aarch64. Is there a fast way to create first buildtree basing on current Artix one?
Imho, the "notes for packagers" document make several assumptions, one of them being that people have previously packaged for arch, it's really not a new-packager friendly document, sorry ... and I'm not an IRC type of person, I don't think I'm the only one.
Also, you expect people to remember the difference between gremlins and goblins? Might be a turn-off for some.
I assume you're using Arch ARM's (https://archlinuxarm.org) repos? Then you could start by building our [system] packages, starting with the most essential ones. If you take a look at our Wiki entry (https://wiki.artixlinux.org/Main/Migration) you'll see which ones are the bare minimum (base base-devel openrc-system grub linux-lts linux-lts-headers systemd-dummy libsystemd-dummy openrc-world openrc netifrc grub mkinitcpio). The list might be outdated, I'm on mobile phone now and can't check. Thus, you can slowly add to them the rest of the repo. Pretty much the same way we did with Arch's repos.
I'd first do toolchain and its depends. Once you got the toolchain, you can build up from there base-devel group.
Building natively? That's quite a task. I assumed he's using the aarch64-linux-gnu-* suite of tools.
It's the best we can do ATM, we're still low on resources and time. I had to work between zero dark-thirty and dawn for quite a few nights just to revamp the site and the rest of the devs are borrowing time from their families / studies / work too.
But, anyway, having packaged for Arch is of the essence; you can't contribute to a repository, whereupon hundreds or thousands of people depend, if you don't know how basic packaging works. To put it in the right perspective, even seasoned packagers from the dev team have botched things once or twice (or more in my case, and I've been maintaining unofficial repos since the era of [openrc-eudev] (https://sourceforge.net/projects/archopenrc/files/openrc-eudev/) and even linux-pf (https://aur.archlinux.org/packages/linux-pf/) back in 2011) - imagine what would happen if inexperienced packagers, in all their good intent, were given access to an official repository without some guidance and feedback.
Having said that, the artools (https://gitea.artixlinux.org/artix/artools) developer is
@artoo and without his instructions on the IRC (nothing beats live conversation) I wouldn't be able to write the documentation. If you absolutely can't join the IRC, we'll gladly listen to your questions or suggestions about the packaging documentation here and try to update it accordingly.
Well, we had to take a quick decision back then about our [testing] and [staging] equivalents. Think of [gremlins] as a place with cute, furry critters that occasionally bite careless travellers and [goblins] as a place full of ugly, blood-thirsty beasts that will rape and kill you, not necessarily in that order.
It was already done by ArchARM developers. I have already built runit, eudev and some other packages i included in aarch64 image i've posted some time ago
Hey
I have lots of free time to spend so i thought i may be useful and can help
however unfortunately i am not really experienced to linux cuz i only started using it this year and i have no idea what PKGbuild is as well, but if somebody's willing to explain then i'll be happy to give a hand, i also have no idea what packaging is unfortunately, but as i said i haven't got knowledge, but i have got time :)
thanks
I'd like to help out too. I've been using arch for a long time but I'm new to creating packages for it.
You can start by maintaining a couple of packages you use at the AUR. The PKGBUILD manpage and Arch wiki entry cover most of whatever you need to know. Some bash scripting knowledge is expected, the rest is covered here (https://gitea.artixlinux.org/artix/documentation/src/branch/master/Notes%20for%20packagers.md).
wish i could know how write pkgbuild for wine and wine-staging
hmm i just checked pkg-build of yay and it doesn't seem that hard to be honest.
there are few things like
makedepends=(
'go
or build() or package ()
that i dont understand but im gonna read about it so maybe ill be able to write something.
edit:
Okay well i can see there's playonlinux in octopi but there isn't dependency wine in AUR list. There is either wine-stable or wine-staging. So not sure if playonlinux depends on wine shouldn't be changed to wine-stable
although i am not sure because wine-stable isn't in depends on although this is wine https://www.archlinux.org/packages/multilib/x86_64/wine/
however there isn't wine available in yaourt -S. but there is wine-stable so i am not sure, but im gonna try to write pkg for wine-stable
ok i am confused now. if there isnt wine-stable in pacman -S but there is in yaourt -S then it's like there isn't wine-stable available in octopi but yaourt is not related to artix so i dont know how to transform wine-stable from yaourt to pacman so it will be available on Artix and in octopi, i have no idea. If there's pkgbuild written for yaourt how can i write one for pacman????
@cynicfm What pacman sees is the distro's repos wherefrom you directly get compiled & built packages. While yaourt sees the AUR (Arch User Repository), which has PKGBUILDs, that compiles programs on your machine.
Why do you want to use `wine-stable` . There is already a `wine` package available? It is just that you have to enable the `[multilib]` repository in /etc/pacman.conf
Yeah sorry, then i have no idea what pkgbuild is cuz i have never seen this before i first entered this forum and seen this topic.
What i understand from what pkgbuild is it is a script that pacman uses while downloading and then installing certain app? And making pkgbuilds for Artix is so AUR available packages that i can install via yaourt, will be written for Artix so they're available via pacman???
And also is there any possibility to see Artix packages pkgbuilds so i can learn from them?? Is for example AUR wesnoth pkgbuild different from Artix wesnoth pkgbuild??? (battle for wesnoth game :) )
Oh okay, thanks for telling me this. Cuz i tried to download playonlinux before via pacman -S but i couldnt. So i thought something is broken. Now getting with pacman -Sy :)
Hello everyone on forum! :)
I am interested to support Artix Linux as person who will maintain packages.
How I can start participate in this?
@cynicfm Artix doesn;t package Wesnoth yet. To look at PKGBUILDs:
- Arch: https://www.archlinux.org/packages/
- Artix: https://gitea.artixlinux.org/explore/repos/
I think you should make it easy to register an account on https://gitea.artixlinux.org
If people had accounts on https://gitea.artixlinux.org, they would be freely able to contribute pull requests to existing packages. You wouldn't have to recruit packagers if https://gitea.artixlinux.org accepted registrations.
You can promote active contributors to maintainers over time and demote dormant maintainers to contributors. This would be a cheap gradual process.
@dawcek Your PM has gotten a reply
@MilkCow Gitea is still missing functionality WRT user and group privileges. If we open registrations there, any user commit would trigger a build and push to our repos, which is not what the community would want. We're still looking for a way to make things work.
Hi,
is there a step by step guide for an example package? If so, I'd love to support you.
br
alex
Creating packages is covered by the PKGBUILD man page or the Arch wiki article (https://wiki.archlinux.org/index.php/PKGBUILD). Submitting packages to our repos is described in Artix packaging documentation (https://gitea.artixlinux.org/artix/documentation/src/branch/master/Notes%20for%20packagers.md). If you're really interested, you should join #artix@freenode and request access to #artix-dev.
I'd like to contribute. Haven't had much luck with responses in #artix and attempting to sync the git repo with buildtree just gives me https://pastebin.com/dv4igDD3 Any help is appreciated. Thanks.
Hi,
I just made my first package "tickr". It's already in AUR, but for testing purposes I made the pkg locally by myself.
First I read the "PGKBUILD" Article and then the "Creating packages" Article on the Arch Wiki. It was not a big deal but some questions occured:
- The dev wrote in his readme that the pkg depends on GTK+ and Libxml2, so I first added GTK3 and Libxml2 as an dependency in the PGKBUILD. Is this the right way? Because after compiling the source and checking the package with namcap it showed me to warnings:
1) GTK 2 should be used as the dependency instead of GTK3, why is that?
2) libxml2 is "already satisfied", what does that mean? - What are the next steps?
I can submit the PGKBUILD I made and the README from the dev, if neccesary.
hey
i am looking forward to write pkgbuilds for some games
this is what i found on arch wiki it's example pkgbuild:
https://git.archlinux.org/pacman.git/plain/proto/PKGBUILD.proto
i only wonder how to check that for example exact game that is not in octopi, what libs and packages does it require?? and what it depends on?? how do you know it?? it's all in readme??
im looking forward to add games to artix repos, because i like them but i am bored... well like i may try... it doesn't seem hard but well i should get hold of some example pkgbuilds and compare them to each other that would be easier
https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot
A lot of dependancies you will normally find in the readme but only by building in a chroot can you be sure you've missed nothing. Errors, when you build it, will give you a clue if anything is missing.
hey
thanks for replies ;). what i am not sure of is what is the difference between arch pkgbuild for wesnoth and 'wouldbe' for artix one?? Is it like for example arch pkgbuilds have depends= and makedepends= uses systemd packages while artix would be just without systemd ones?? so artix would need own pkgbuilds for depends and makedepends??
sorry i am simply not sure what would be difference between artix and arch pkgbuild for wesnoth for example.
And also i would like to know what has chroot to do with writing pkgbuilds, is it to build specific package on my system under chroot?? So for example if i wanna compile certain game from source, it's best to build it in chroot? and then if i built it that way, i'm gonna know that everything is ok?? and it will also give me errors output is something is not right??
thanks
It depends on the package. Some arch packages abusively depend on [lib]systemd, others use systemd-related configure options. For the latter, a
--disable-systemd flag is usually enough to have them cleaned. The former sometimes can be cured by depending them on [lib]elogind.
Take the
dbus diff for example, which is harder to keep clean and needs an additional patch:
--- dbus.arch 2019-02-07 21:33:25.010297658 +0200
+++ dbus.artix 2019-02-07 21:34:12.640308698 +0200
-depends=(libsystemd expat audit)
+depends=(libx11 libelogind expat audit)
-makedepends=(systemd xmlto docbook-xsl python yelp-tools doxygen git autoconf-archive graphviz)
+makedepends=(elogind xmlto docbook-xsl python yelp-tools doxygen git autoconf-archive graphviz)
+ patch -Np 1 -i ${srcdir}/dbus-enable-elogind.patch
+ --with-system-pid-file=/run/dbus/pid \
+ --with-console-auth-dir=/run/console/ \
+ --enable-inotify \
+ --without-systemdsystemunitdir \
+ --disable-systemd \
- --disable-static \
- --without-x
+ --enable-elogind \
+ --enable-x11-autolaunch \
+ --disable-static
Most packages, however, are way easier to maintain as, thankfully, don't really need or want systemd to work.
Hi,
I maintain my own distribution for servers based on LFS and with pacman as package manager for years.
I think, I might be of use for you. Contact me
Cheers
casaubon
Why don't you register a nickname at Freenode and join #artix? You'll be invited to #artix-dev and meet the rest of the Jedi Council...
well i have lots of free time to spare, and i use artix as the daily distro so im thinking i would like to contribute with this if i had knew how. im in the process of typign every step of pkgbuilds down into notepad (so i can remember it better), but i also read here that bash scripting is helpful or necessary??
My brain of amateur IT guy tells me: why just don't copy pkgbuild of arch wesnoth and make it as artix??
to be fair writing these pkgbuilds sounds like easy stuff, but i think i lack theory. isn't it like writing one pkgbuild takes about 30 minutes??
i am still not sure how to know what are dependencies of certain aur packages that i would like to get into artix. i have never used chroot command apart from when i was installing arch and only fro like 5 minutes.
I understand the importance (i think) and i think that every package here on artix should be from artix repos, not from arch, but am i wrong??
i think im gonna have to learn bash scripting first, and i wanted to learn it anyways. for example i need to find something about how to write a script that i can run and it will run few commands (i have some for hdd and cpu to save battery).
Is there any nice website where they explain how to write scripts in bash??
I use artix runit with LXDE and i am amazed how fast my laptop is now and it doesn't seem like im gonna change this or use different OS any soon, cuz i feel comfortable here. However because i am new to linux i don't really know what i could do to make it 'better'. I have ideas like to write pkgbuilds for linux games that i played past few months, i am also bored so if i knew how, i could even find packages on AUR and just rewrite them into artix.
Perhaps before posting again in this thread, i am gonna try write pkgbuild for some simple package and post it here and ask questions ;)
thanks for reading and explaining ;)
edit: oh last question, if i manage to write some pkgbuild is there any way to test it to see if everything is alright?? before i send code to forum??
@cynicfm I will suggest the same thing I told someone else on this thread: If there is any software you use that isn't in the repos or the AUR, make a fresh PKGBUILD for it and upload it to the AUR. Use the Arch wiki to figure out how to write them, and you can always ask on the IRC channel (#artix) or even #archlinux-aur. I'd be glad to help if you run into trouble.
ok cool
well i am thinking about this all the time but i am still not ready mentally for this. I have no idea what packages aren't there in Artix repositories that i would use, but i am a type of playing games person, so i think i am gonna try mess with free/open-source/libre games that i can find online and try write pkgbuilds for one, perhaps flare (flarerpg.org) will be the first one. Not sure how i am gonna find out what are depends() but i will sort it out ;).
Thank you very much.
I'd like to help, if it is still possible :-)
Of course it is, thanks for your offer. Please, join #artix at Freenode (you need a registered nick) and ask to be invited to #artix-dev. It's better to talk these things live.
First of all: I am new here and I want to say hello! :)
Second: I had an eye on artix since months and I really would like to install ot as my 2nd daily driver.
Third: I used to use arch years ago and switched completely to void linux where I contribute active as package maintainer as well as for alpine linux. But I want a more recent (glibc) based rolling release distro and I love the amount of packages available on arch.
Last but not least: If I really take the step to get into artix' family, I really would like to contribute as package maintainer. So is there still need for?
Thanks for any answer. Looking forward! :)
Yup, there is, especially for people who already have experience with maintaining packages. :)
That said, ideally, since we have many applications, we train applicants, many are willing but start from scratch in term of knowledge and experience.
@artoo Very well. Like to read that and I am willing to help to train as well as package myself. That said: I never built with arch's build system but I guess I will get into it soon but may require some help too at the beginning.
Guess it's time to get my artix setup up. :)
EDIT: So how exactly would I get access to your repositories on gitea?
Since you've got experience with PKGBUILDs, all you need is to familiarize yourself with artools. The helpers take care of syncing, updating and pushing to the build server. Have a look at the documentation (https://gitea.artixlinux.org/artix/documentation/src/branch/master/Notes%20for%20packagers.md).
It's best you join our Freenode channel,
#artix-dev. Register a nickname, join
#artix and request an invitation. Please, be patient until a dev is around and invites you. It's better to talk live for packaging.
Oh this Artix was my first experience with Arch Linux and i had no idea what PKGbuild was.
Now since i have been using arch linux for a while, i often download AUR snapshots and use makepkg -si so i know a bit more about it than i used to however somebody told me on artix-dev that you need to handle GIT as well.
I am willing to help, already made a package to support openrc
How do I pull request to packages
We don't do PR, you have to join the packaging team.
What openrc package did you make?
I made a shadowsocks-libev package for openrc, I can port more if needed
Please, read https://forum.artixlinux.org/index.php/topic,512.msg7809.html#msg7809 and join our IRC channel.
I want to help
After my installation issue is resolved, I may be able to help.
I am a newbie artix user (previously was using Antix and before that Debian). Please count me in
count me
but i am novice :-[
To
@artik &
@zenobit: your offers are greatly appreciated but, unfortunately, there's no easy way into this. You need to familiarize yourselves with PKGBUILDs, which means you should try to maintain a couple of packages you use on the AUR. Once you're ready, you will know it.
i dont have much free time, but love artix , hate systemd , and would like to give a hand when possible.
Hi! i've been using artix for a while and i've used Arch for years, and i would like to contribute sooo... count me in!
@shadowstep &
@TommasoPlease, join #artix at Freenode (you'll need a registered nick because spam) and ask to be invited to #artix-dev. Not everyone is always online, but eventually someone will. Cheers!
[EDIT] After the Freenode takeover, Artix has moved to Libera network: irc.libera.chat -- TLS/SSL ports 6697, 7000 and 7070.
Sure, I can probably churn out a few. I've written a lot of slackbuilds and I have done a few PKGBUILDs at one point so it shouldn't be too much trouble for me to figure it out again.
I would be interested. Is it required that packaging is done on Artix?
I can for sure do from my PC but i have a couple VPS's that are running Arch. Would those work as well? I ask only because i sometimes have to give up my PC to my son but would still be able to access VPS to do packaging.
I've used Arch for quite some time. Have some understanding of PKGBUILD's but have never really created one from scratch.
Well, good intentions is as good a start as any. All current developers and packagers started following the same procedure (https://forum.artixlinux.org/index.php/topic,512.msg3968.html)!
I wouldn't mind helping at all, I just need to read up on how to do it.
A minimum level of expertise in bash, PKGBUILD, git and patch/diff is needed. If you can follow the Artix packaging documentation (https://gitea.artixlinux.org/artix/documentation/src/branch/master/Notes%20for%20packagers.md) without too many questions, then you're probably up to the task and can follow the instructions above (https://forum.artixlinux.org/index.php/topic,512.msg8772.html#msg8772). Thanks for your help offer.
I want to help too ;)
yo también podría colaborar en la medida de lo posible no tengo experiencia ni mucho menos conocimiento en bash o git más con una estudiada a bash y git creería que podría colaborar siempre y cuando ustedes me lo permitan
I would like to contribute to package maintenance as well!
Hope everyone's having a good day :)
Please, follow the directions above (https://forum.artixlinux.org/index.php/topic,512.msg8772.html#msg8772).
Hello! I'm a software developer and want to contribute to this amazing distro that I just found. Which packages need maintenance, and how may I get started?
Why don't you just follow the last post before yours? :D
I tried lol. That links to https://forum.artixlinux.org/index.php/topic,512.msg8772.html#msg8772, which says:
That "same proceedure" part linked to https://forum.artixlinux.org/index.php/topic,512.msg8772.html#msg8772, aka to itself... ?! So I was a bit confused.
Well, my click led to post #85!
Oh huh, weird. That makes much more sense, thanks! Will do soon
Hello, i want to help in Artix Developement
@nous are you still looking for packagers :)
Is this still needed, I am a retired Manjaro user. Tired of systemd.
@TheCynicalLiger @isak https://forum.artixlinux.org/index.php/topic,512.msg8772.html#msg8772
As a reminder, a certain level of expertise is expected of any aspiring packagers and a much higher still of developers.
Have to learn PKGBUILD again, but I can help
I already manage a good amount of AUR packages, I can help too.
Just migrated from the OpenBSD community. How can I be of service?
@monokrome @shoober420 @gnubian @Ye_Scuti Thanks for your offer to help, the procedure remains the same: read this post (https://forum.artixlinux.org/index.php/topic,512.msg11944.html#msg11944) and the one it links to.
Hi! I'm able to help. What can I do for this precious distro and community?
I volunteer as a tribute!
Please, don't make me repeat myself! Follow the instructions and prepare to pass the audition.
Moin! :)
I would like to participate.
Currently I'm trying to build a icing2 package, which I would also maintain
(current branch https://github.com/bodsch/aur-icinga2/tree/feature/support-artixlinux).
Hi @nous,
I am also interested in helping. In particular I'd like to explore packaging an Artix Libre Kernel. Let me know the best way to proceed.
LinuxFan
@bodsch @LinuxFan https://forum.artixlinux.org/index.php/topic,512.msg11944.html#msg11944
Hi Nous,
@nous I have registered at Freenode as nixman and have requested #artix-dev membership.
LinuxMan
That bit of info should be updated to reflect the massive exodus from Freenode to Libera.chat since the recent hostile takeover of Freenode.
It will, once the exodus is complete. Things seems to go slowly nowadays...
here i am send me
@machfour https://forum.artixlinux.org/index.php/topic,512.msg3968.html