I agree with Martin here, I see no benefit in merging gtk in.
Schanzenbach, Martin transcribed 4.6K bytes:
> As an example: Look at how large projects like GNOME are developed.
> Nobody would even dare to put _everything_ in a single repository. That would
> be preposterous.
> The only project I
As an example: Look at how large projects like GNOME are developed.
Nobody would even dare to put _everything_ in a single repository. That would
be preposterous.
The only project I could think of that takes such an approach is systemd.
I know that you grothoff despise this project especially and
Yes, I do not think this is a good idea at all and is contrary to the initial
motivation of this thread.
We already agree the from a user perspective, the packages (.deb/.rpm et al)
should ideally be split into
the respective services/applications and, of course, also Gtk+. For sane
dependency
On 2/7/19 3:21 PM, Hartmut Goebel wrote:
> Am 02.02.19 um 16:09 schrieb Christian Grothoff:
>> And I wonder if it wouldn't make sense to have the gnunet.git
>> configure.ac test for Gtk+ and *if* libgtk is detected, _then_ build Gtk
>> GUIs that are _included_ in gnunet.git, instead of requiring
