Hi AUR enthuasiasts,
I'm the co-maintainer of depot-tools-git.  Two weeks ago that package is
flagged as out-of-date, but I didn't receive any notification mail - not in
Spam either. For other packages that I'm the only maintainer, out-of-date
notifications are well sent. Is it an aurweb bug or just an accident that
my inbox losts the mail?
My name is Giancarlo Razzolini (grazzolini) and I would like to become a TU. Before anything, I want to thank Jelle van der Waa for agreeing to become my sponsor.
I'm 33 years old. I am a developer and infrastructure manager at my own company. I have been using Linux since 1999. Despite my name, I am not Italian, but I'm Brazilian (of Italian descent). My first experience with Linux was with Conectiva Linux, but soon I moved to Slackware, where I stayed for many years. For work reasons, I ended up using Ubuntu for some years. In 2013 I moved to Arch, and it was love at first sight. Or better, at first use.
Right from the beginning I started to contribute, first helping out with the wiki. Later, when I found out about the simplicity of creating and maintaining packages, I started to put some on the AUR. Also, I adapted some tools I had developed for Ubuntu initramfs system, to Arch. Also, I created new ones. Most of them are related with remote unlocking of an encrypted root partition, so lots of early userspace networking. I am also very active on IRC.
Recently I also subscribed as a tester, and I do give signoff's to the packages I am able to test. If I become a TU, I would like to bring some of the packages I maintain on the AUR to community, specially:
I would also like to bring some of my own project's packages, specially:
I am willing to adopt packages also. From the list of orphaned packages, I am willing to adopt right away terminator and all it's dependencies.
Thanks in advance,
I recently started maintaining small AUR packages (basically just
updating version numbers on git packages and so on), and I came into a
little situation when updating the boost-compute  package.
The package is basically a header-only library, typically providing
files under /usr/include/boost/compute. The package can be installed
without trouble using the usual makepkg + pacman -U combo.
However when I tried to install the package using yaourt, I realised a
little something: the package depends on boost , which now seems to
provide the boost-compute library as part of its own code. This means
that when I install boost-compute using yaourt, it first pulls boost
from the extra repositories, which brings the include/compute/ files,
and creates a conflict when boost-compute comes afterwards (yaourt seems
to detect the conflict and therefore stops).
I'm guessing the reason why the makepkg approach works is because it
doesn't run these checks, and the boost files are simply overwritten
(the PKGBUILD runs a simple cp). So here's what I'm hesitating about:
- Should I ignore yaourt, and keep maintaining boost-compute separately?
I guess this could be of some use if at some point the library gets
updated and Boost doesn't bring the changes in immediately (those in a
hurry could simply overwrite the Boost files with pacman -U).
- Should the boost-compute package simply be deleted, since it requires
boost anyway, and Boost is probably going to update the compute code
Thanks in advance for your advice!
Julien JPK (0xC3075A58)