Add Ionic as a maintainer? about paludis-gentoo-patches HOT 8 CLOSED

I'm open to it eventually going back into ::gentoo if we can find good maintainers for it, too. So having negril on board would be helpful there.

from paludis-gentoo-patches.

Yes.
I think it's a right thing to do.
I've sent him an invitation.

from paludis-gentoo-patches.

@negril
Invited.

from paludis-gentoo-patches.

Could you add me as well?

I have more changes on top of Ionics and my work and rebased it on top of the current upstream master. See https://github.com/negril/paludis/tree/gentoo/build
or https://gitlab.exherbo.org/negril/paludis/-/tree/gentoo/build .

The eapi8 branch is at https://gitlab.exherbo.org/negril/paludis/-/tree/gentoo/feature/eapi8 .

from paludis-gentoo-patches.

What would maintaining it involve?

from paludis-gentoo-patches.

Doing the fixes both you and @Ionic have been doing already, having a single repo where we have all the patches, and being reasonably responsive to bugs on Bugzilla.

In this case, what I meant was "we really want a single "upstream" for a working Paludis", and it's a lot easier if the two people actively working on it have access to the same repo.

from paludis-gentoo-patches.

My idea was to be as close to upstream paludis as possible and then have our own branch onto of it. Hence the repo on their gitlab. We could use that or something on here. If and when Ionic has input we could figure that out.

My up-to-date ebuilds are at paludis-gentoo-overlay.

The python and ruby build is fubar though and needs to be looked at.
And we still have 4 tests that fail afaik.

from paludis-gentoo-patches.

Thanks. I've been oddly quiet on this mainly due to work reasons. Just plainly had not time to work on it (or, for that matter, even update my machine.)

My vacation is coming up at the end of December and January, so I hope that I'll be able to work on it in a more focused way.

My idea was to be as close to upstream paludis as possible and then have our own branch onto of it. Hence the repo on their gitlab. We could use that or something on here. If and when Ionic has input we could figure that out.

I mostly agree with that (which, btw, is why I want to keep changes minimal and didn't integrate your test suite mechanic changes - while I do like them personally, they aren't really changing anything other than making adding tests more easy and using a cleaner, newer API). I'm not a huge fan of calling the Gentoo part of paludis a fork - my goal would be to integrate our changes back into the main paludis repository - not as a separate branch, but right in the main/master/nomdujour branch. While it doesn't really have any implications for exherbo itself, it would make maintaining paludis a lot easier for us, since we wouldn't have to constantly rebase against their main branch. So far, they haven't thrown out support for Gentoo-style EAPIs and ebuilds, which gets my hopes up that they would eventually merge good-quality code back in, as long as it doesn't break their use cases.

from paludis-gentoo-patches.