Hi thanks for your insights. I guess python-pygccxml is not directly needed here in Debian Med. On ITK’s side, pygccxml is present in ITK’s repo as a subtree. So it is not needed as a dependency, and there is no plan to change this.
I’ll leave the decision up to you. I personally recommend people to install it through pip, which is the fastest way to get it. Having a debian package of course better; maybe as there is already one it would only need an update to the newest version. I am not ready to maintain the package myself for the moment, as I have other ongoing projects. But I can help if there are any questions. Tell me if you want to update the package; I’ll send a mail to Aron as soon as the new version is out. Regards Michka > On 13 Aug 2015, at 13:30, Aron Xu <happyaron...@gmail.com> wrote: > > Actually I'm seeking to orphan the package as I don't use it myself > anymore, but it's not a burden so far so that I haven't done it yet. > If there are people interested in adopting or co-maintaining it'll be > appreciated. There's no any form of repository at the moment and I can > create one if no one else is more interested, :) > > Thanks, > Aron > > On Thu, Aug 13, 2015 at 3:29 PM, Andreas Tille <ti...@debian.org> wrote: >> Hi Michka, >> >> I keep the Debian maintainer Aron Xu in CC. Gccxml was maintained as a >> predependency of some Debian Med package by the according team. I'm not >> aware that python-pygccxml has any reverse dependencies in Debian Med >> but surely ITK is of interest. Could the ITK people please raise their >> opinion whether it would be good to team maintain this package here as >> well. Aron, would you consider using some common Git repository either >> in Debian Med or collab-maint? >> >> Kind regards >> >> Andreas. >> >> On Thu, Aug 13, 2015 at 08:37:13AM +0200, michkapop...@gmail.com wrote: >>>> On August 5, 2015 03:29:30 PM Sébastien Jodogne wrote: >>>> >>>>>> I will try hard to get the script into VCS tonight and then I will >>>>>> welcome >>>>>> help in testing the builds on dependent packages. >>>>> >>>>> Great! Let me know when things are ready. >>>> >>>> OK. The gccxml package is updated with a wrapper around castxml (the real >>>> binary is renamed to gccxml.real). >>>> >>>> Still working on testing build-deps with it. Sadly, pygccxml fails :-( >>>> >>>> -Steve >>>> <signature.asc> >>> >>> Hi >>> >>> I was told someone mentioned pygccxml here :) >>> >>> I am the current maintainer of the project >>> (https://github.com/gccxml/pygccxml <https://github.com/gccxml/pygccxml>). >>> During the last months I worked on the integration of CastXML in pygccxml >>> and I am >>> almost done. Basically, there were around 80 unit tests failing, and I am >>> down >>> to 10 failing tests. The core unit tests are running, and ITK already uses >>> pygccxml >>> internally. So as long as one does not do fancy stuff, it should be ok. >>> >>> I delayed the new release in the hope to be able to fix the remaining >>> tests; but this >>> takes a lot of time (as I did not write pygccxml in the first place, I am >>> discovering >>> the code). But I think there is some pressure to release a new version with >>> basic >>> support so people can start using it. I even heard from 1 or 2 people which >>> are using >>> the current unstable version in combination with pyplusplus to build their >>> project >>> using CastXML instead of GccXML. >>> >>> I will publish a new pygccxml version (1.7.0) in the next weeks. The >>> package name >>> will not change, and is backwards compatible with gccxml. I will >>> temporarily disable >>> the failing tests when running with CastXML. >>> >>> Please tell me if I need to notify someone when the new version is out or >>> if there >>> is something I can to to help the packaging. pygccxml will also be available >>> through pip. >>> >>> Regards >>> >>> Michka >>> >>> >>> >>> >> >> -- >> http://fam-tille.de > > > > -- > Regards, > Aron Xu