Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » Releasing U++ » Archlinux AUR (Considering adopting U++ packages)
Re: Archlinux AUR [message #47917 is a reply to message #47913] Sun, 23 April 2017 22:03 Go to previous messageGo to previous message
Eremiell is currently offline  Eremiell
Messages: 5
Registered: April 2017
Location: Prague, CZ
Promising Member
mirek wrote on Sun, 23 April 2017 19:37

Definitely. To dig into the issue a bit more, I believe that U++ developers responsibility should end at producing tarballs. Distro specific issues are currently being resolved by community and we provide links in Downloads pages just for convenience.


I mostly agree, though it's always good to know, you have some support, both theoretical as in "go on" and practical as in the few small changes I asked for. Mostly so that if some issues come up in the future (the build completely breaks, I need some minor meaningful adjustment like the checksums, or whatever) I can trust to have sensible ways of reporting and resolving the issue.

mirek wrote on Sun, 23 April 2017 19:37

All good points. Do not expect it to happend overnight, but I will put to this on high priority. If it is not done in next 14 days (and you are still around:), please poke me.


I will. Wink

mirek wrote on Sun, 23 April 2017 19:37

DDUMP is doing exactly what it is supposed to do. If you have encountered that error, it more or less means this nightly is broken and you have to wait for next nightly.


Yes, I understand that. That was just a minor side note and an expression of a hopeful wish from packaging side of things that this (or similar) macro will remind contained in one place and not spread through the codebase. You should of course prioritize the development needs and ignore this wish completely should it be an obstacle to development. There's always more bash magic to fix stuff around for packaging.

I have an ugly deadline tomorrow, which I have to fulfill before going full crazy on this, but I have the core stuff working as is. Basically it downloads, compiles and packages alright for me, but I noticed some parts of the PKGBUILD are not in good shape, using potentially wrong, deprecated and misleading settings, so I want to polish it to conform the packaging rules first. (I may also be wrong with some of them. Let's say I need some time alone with it, the packaging guidelines and some tea.)

I'd like to find time to push the new builds tomorrow evening or during Tuesday. I'll let you know.

One more possible idea, which I expect to be more complicated and probably lower priority (but I'd love to be wrong):

I believe, the github repo is generated by some autonomous script and no one is actually mirroring that by hand, but if you were able to export some meaningful git tags for stable and nightly versions, that might be an interesting alternative for packaging too, especially for nightlies, which change often anyway. But tarballs, especially if you add the mkfile and checksums, are completely alright of course.

Cheers and seeya around,

Eremiell
 
Read Message icon5.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Tarball issues
Next Topic: size unzipped download installation
Goto Forum:
  


Current Time: Tue Jun 11 03:37:08 CEST 2024

Total time taken to generate the page: 0.01855 seconds