Seyed, On Sunday, November 30, 2025 12:52:32 AM Mountain Standard Time Seyed Mohamad Amin Modaresi wrote: > Hi Soren, thank you! > > I fixed the symbol and interpreter problems, > > I think upstream doesn't fix these problems, they even did not fix pkgconf > file! this issue was reported two years ago! > > BTW I reported it to upstream. > > > For tests, because of test, build was failed, so I skip it. > there is no problem, I even compiled https://github.com/alainm23/planify/ with > the package, so the package works. > > for examples, they were installed in /usr/share/devhelp/books/ by default, but > most of devhelp docs in other packages are installed in > /usr/share/doc/PACKAGE/, so I changed the default install path.
This package is more complicated than the previous things we have packaged, so it is going some time to work through all the issues. I say that just so you don’t get discouraged as we go along. We will eventually get to the end. Because of the complexity, I think it is best to handle only one or two issues at a time so that things don’t get lost. The first big question I have is why there is a binary package named libgxml-0.20-2.0.2? Typically this would be named libgxml-0.20-2. One effect of this is that the name of the binary package will change every time there is a SONAME bump, which helps with the transitions. But we don’t want it to change when there isn’t a SONAME bump, because that would result in needless passes through NEW, with their associated delays. -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
