Arch Linux User Repository

@Rhinoceros - the alpm12 aur project has been created. you can use my patch, and apply the minor PKGBUILD mods (add patch file, add call to patch for new patchfile, and substitute the pacman dependency with alpm12). re-version to whatever makes sense.

for clarity, the PKGBUILD and patch file are located here - https://sourceforge.net/projects/bluestarlinux/files/extra/kalu-kde/alpm12/kalu-kde/

@Thulinma - np. enjoy. @Rhinoceros - a patch file needs to be generated for the alpm12 version of kalu-kde. i'll take a look at what it'll take. also, if you want to adopt the alpm12 project, you are welcome to it. it's needed to build and run a working kalu-kde from source. the source code for it is included in the alpm12 tar bundle in the alpm12 directory.

@Rhinoceros - i have a patch file for kalu-kde and the modified PKGBUILD. they're at https://sourceforge.net/projects/bluestarlinux/files/extra/kalu-kde/alpm12/kalu-kde/

the PKGBUILD will need minor tweaking to restore checksumming (i replace with SKIP for testing purposes). i've tested the patch and PKGBUILD and it built without any issues. i still have to create a github project for alpm12, which is now a dependency (and make dependency) for kalu-kde.

EDIT2: alpm12 is now a github project: https://github.com/jghodd/alpm12 - it has a 1.0.1 tag version available for download. next i have to figure out how to create an AUR project.

EDIT3: go here to find the alpm12 project files (for the AUR) - https://sourceforge.net/projects/bluestarlinux/files/extra/kalu-kde/alpm12/alpm12/ - the PKGBUILD and alpm12 header files are there (needed for pkgbuild/makepkg). they are complete and will build alpm12-1.0.1, pulling the source from the github project.

there is still some minor work to do on alpm12. although what's there works as expected, some things can be done automatically via make/config on the 'make install' if i can find the right places to modify. it needs to build libalpm12.so.12.0.2 instead of having to rename libalpm.so.12.0.2. it also needs to install alpm12.h and alpm12_list.h from the project source instead of providing them as project extras and doing most of the real install work via PKGBUILD. the make/config files/templates are obviously IDE-generated and more complicated than they need be, so finding the def thread that gets you where you want to be isn;t always obvious. i'll keep on looking for these solutions, but i'm going to slow down a bit. i'm running kalu-kde perfectly right now, built from scratch against the alpm12 (v1.0.1) project build.

i haven't created an AUR project in a couple or more years. i can figure it out all over again, or anyone who wants to can feel free to create the alpm12 project from the files i provided...

EDIT4: fixed one issue in the PKGBUILD and generated the .SRCINFO file. they're all available in https://sourceforge.net/projects/bluestarlinux/files/extra/kalu-kde/alpm12/alpm12

Thanks again both of you. I've added you both as co-maintainers, so feel free to push changes here when you have a working version.

@jghodd Thanks! Downloaded the alpm13 version and will see if I can patch it up to work as soon as I have some free time.

OK. https://sourceforge.net/projects/bluestarlinux/files/extra/kalu-kde/

there are 2 directories there - alpm12 and alpm13.

• the alpm12 directory contains the packages alpm12 and kalu-kde. these are buildable and installable. and work.
• the alpm13 directory contains the unfinished source upgrade to alpm13.

right after my last comment, i discovered that someone else has created a libalpm12 aur project. it is incomplete and will not allow the building of kalu-kde. it could probably be used with a pre-existing kalu-kde binary. so... i had to change my original libalpm12 project name to alpm12. this one includes the header files and a correct .pc file. also, the alpm12 project is a significantly pared down version of pacman-5.2.2 - source files removed, make/config files modified. this has not been made into an aur project yet. some of what i've done in the alpm12 project PKGBUILD can most certainly be done via project makefiles - i'll get to that when/if i can. if anybody else cares enough to change the makefile templates to produce a libalpm12.so.12.0.2 library, please go for it, and remember to change the PKGBUILD accordingly (at the moment, i build libalpm.so.12.0.2 and rename it via the PKGBUILD).

@Thulinma @Rhinoceros - i have a working kalu-kde. i have to tweak a couple of things in my new libalpm12 package, but i'll be able to put together a tar file for y'all soon. i'll also include the source for the aborted attempt to move to alpm-13.

@Thulinma - i may have gotten further, but i also hit a wall. it's going to take some deep diving to resolve the download callback issue (including the progress numbers). kalu was using the same callback function for both progress and download - the progress callback which, incidentally, still has the same function signature. it's just that you can no longer use the progress callback for the new download callback function. we may be overthinking this. i don't know. i'd kinda like to see what pamac and octopi do to resolve it. the respective developers for those apps are much more familiar with the mechanism(s) and we can follow their lead. so, i decided to stop and take a more expeditious route - i pulled the pacman-5.2.2 code and worked the makefiles and pkgbuild to produce a libalpm12 package which contains only libalpm.so.12 and libalpm.so.12.0.2, and a .pc file for the new package (called alpm12). just finished that last night and will test soon after moving alpm-v12's alpm.h and alpm_list.h into the kalu-kde codebase, and tying those in. that buys time. just make kalu-kde dependent on libalpm12 (as a 4.3.0-x version). if we can fix the kalu code to work with libalpm-13, that, i think, could be a good time to advance the kalu version. i can bundle up what ive done and drop it for you. i'll leave the url here, as an EDIT, whenever i can get it there.

@jghodd It sounds like you're further than I was already. Are your changes available somewhere so I can see if I can help figure out the remaining parts?

I'm pretty sure the part you're talking about is used to show the overall download progress bar, which now that pacman supports simultaneous downloads no longer is as trivial as it used to be. We can probably calculate it from the progress callback, or worst case just remove/disable the progress bar altogether.

@jghodd Thank you so much for all the work you've done so far. A pity these issues seem difficult to overcome. Hopefully you or @Thulinma can come up with something. Thanks again.

@Rhinoceros - i've been able to address all issues except two - and one of them is a big one. per the pacman README:

[REMOVED] - old TotalDownload implementation - alpm_cb_totaldl - alpm_option_get_totaldlcb() - alpm_option_set_totaldlcb()

[CHANGED] - alpm_cb_download pass event and data

these changes are not simple ones. i won;t be addressing them tonight. i'm going to see if i can come up with a wrapper solution for the alpm_cb_download issue, but thus far i have no idea how to fix the totaldl problem - it's use is important to the current source code, but the means to provide some value has been removed. i'll have to see if i can find some other way to get to the value and how it's now being used. a total rewrite would be difficult, to say the least.