Re: EFL/1.18, Enlightenment/0.21 updates
Hi,
I won't test/review, unless you want it to be uploaded in Debian
(with an RFS bug), sorry!
>1) Standards-Version is 3.9.6 because the test suite may perform remote
>network operations. I've tried to locate and disable these, but I'm not
>sure if I've gotten them all.
network is disabled regardless of the std-version I guess, however I would
bump it and then fix failures in case
>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)
>3) Some patches are missing dep3 details as I've been unable to
>determine their authorship. Similarly, I've been unable to find license
>info for the debian/* files themselves.
this isn't usually a real problem, and for sure not a regression
(you might find help with git log -p filename)
>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?
it might make sense to have one single source package providing all
the binaries, in case they have no sense to exist outside the source
package,
but this means that fixing a line of code in one of them means
a new upstream release or a Debian upload for the whole package.
the other way is to keep them split, but you should prior understand
the reasons for them being merged into a single package.
>Andreas Metzler deserves thanks for beginning this upgrade effort, and
>for helping with numerous situations I didn't know how to handle.
so you might already have your sponsor :)
>Thanks for any comments/suggestions,
sorry for providing almost none :)
G.
Reply to: