On Fri, 14 Feb 2020 at 20:39:54 +0100, Andreas Henriksson wrote:
> (Please also make sure to look into all the deprecated notices that is
> being spit out during build. Those will likely become an issue in the
> not too distant future. But first you might want to reconsider if you
> really have the resources for taking on the task of becoming your own
> upstream.)
All the same considerations apply to liboobs and system-tools-backends,
which are also former GNOME projects. Taking over as upstream developer
of gnome-system-tools doesn't really make sense unless you do the same
for those two packages.
Again, consider whether you have the resources to maintain these. At this
point they have at least a decade of technical debt since the last time
they were actively maintained. In particular, they depend on dbus-glib,
which has been obsolete since the addition of GDBus to GLib in 2010.
Nothing else seems to depend on any of this family of packages, so
if you do take them over, combining the former gnome-system-tools,
system-tools-backends and liboobs packages into one big source tree
is likely to be simpler than keeping them separate.
smcv
