On 09/12/2016 05:49 AM, Gianfranco Costamagna wrote:
I won't test/review, unless you want it to be uploaded in Debian
(with an RFS bug), sorry!
That's cool - thanks for taking a look at my questions.
2) The previous maintainer hasn't been active, so my work is not in the
alioth pkg-e-devel repo. I've left the Vcs-* fields pointing at the
official repo but I'm currently pushing to:
https://github.com/rvandegrift/efl.git
https://github.com/rvandegrift/e.git
did you try to join the team?
the maintainer has been pinged by MIA team, and said "will fix in one month"
"2016-08-24: willfix 1m"
so, in case he orphan the package, you might ask to maintain them
(or, since I cc'd him, maybe sponsor/review your work)
I've been in occasional contact with Albin, and hope he'll have a change
to review & sponsor. I just posted here in case anyone was interested
and had feedback in the meantime (sorry if that's off topic!)
4) As of 1.18, the efl source package includes previously separate
source packages. I don't know if anything special needs to be done in
this situation.
I don't know, how do they evolve? all together or separately?
Upstream has opted to merge the source packages together to ease
building and distribution. Didn't see a benefit to reversing that.
I meant: is there anything extra a good source package should do when it
absorbs another?
Thanks for any comments/suggestions,
sorry for providing almost none :)
Still managed to be useful :)
Ross
