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

Re: Packagers wanted!

Reply #60
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:
Code: [Select]
--- 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.

Re: Packagers wanted!

Reply #61
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
Whenever you find yourself on the side of the majority it is time to pause and reflect.
Mark Twain

Re: Packagers wanted!

Reply #62
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...

Re: Packagers wanted!

Reply #63
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??