Home » Developing U++ » Releasing U++ » Archlinux AUR (Considering adopting U++ packages)
Re: Archlinux AUR [message #47931 is a reply to message #47928] |
Tue, 25 April 2017 01:05   |
Eremiell
Messages: 5 Registered: April 2017 Location: Prague, CZ
|
Promising Member |
|
|
dolik.rce wrote on Mon, 24 April 2017 21:21
Maintainer of the AUR packages speaking here I'm sorry I didn't reply right away when you flagged the package in AUR. Unfortunately, I'm rather busy lately and I must admit I didn't take proper care about the packages. Feel free to contact me directly if you're interested.
I acted mostly as upp-nightly and upp-git (and their umk and theide counterparts) became orphaned after me poking around. I still hoped for you to pop up. It's not my first round around flagging outdated packages, commenting on breakage and stuff not working and dropping wild PKGBUILD patches around. I got used to some maintainers acting in matter of minutes and other in days and weeks.
dolik.rce wrote on Mon, 24 April 2017 21:21
I'd be more than happy to transfer those packages into good hands of another Arch user who will have more time to keep them up to date.
It was more or less sheer pragmatism to volunteer, as I want these packages to work and I'm hacking around the PKGBUILDs already anyway, so why not share the work with others. I don't really wish to take the packages from you, if you're up to maintaining them further (talking mostly about stable now, the other two branches are unmaintained, orphaned and originated with fusion809 not you, but if you wish to take those under your control, I'd respect and support that).
On the other hand, if you feel you don't have time to maintain them, I could as well take care of all three branches, not much extra work.
I'm also ready to share the duty, so whoever notices the trouble first and has a slice of time fixes the fire.
As a side note, I'm designing the nightly and git channels as auto updating, grabbing new versions on fly without hand patching the PKGBULD in AUR unless something changes, similar to firefox-always-nightly AUR package or most of git packages around. The git package works so already after some fixing, as it previously read the AUR repo version and not the u++ repo one, so it never rebuilt. I'll fix nightly channel so once the checksums and version file are up, hand patched for now.
Still what I said before, I need to go though some parts carefully and slowly with packaging guidelines, as I fe. don't think, the package should be really flagged as arch: any, as it becomes platform dependent after build(), so it should probably list arches one by one.
dolik.rce wrote on Mon, 24 April 2017 21:21
That file is a wonderful thing, but it is not really needed for the basic packaging. Less then a year ago, Amrein did a many fixes in the generated makefile that is included in the tarball when he was working on RPM packages. It should be fairly easy to use the regular makefile for Arch packages as well.
I'll look into it, though I'd still prefer the file to just be packaged, as it "just works" and it's some 20kB decompressed.
The current package also sports two custom files, GCC.bm and theide.install, which seem not to come from repo. The second one seems to be quite simplified version of similar file in debian directory, the first one apparently comes into the compilation process and I guess is needed for the mkfile procedure. If using the regular makefile would drop need for this file, that would probably be nice. So yes, I'll look into it.
Cheers,
Eremiell
|
|
|
Goto Forum:
Current Time: Tue May 13 07:45:05 CEST 2025
Total time taken to generate the page: 0.00782 seconds
|