On Mon, Sep 11, 2017 at 11:07 AM, Miroslav Suchý <msuchy(a)redhat.com> wrote:
Dne 8.9.2017 v 14:39 Neal Gompa napsal(a):
> On Fri, Sep 8, 2017 at 8:36 AM, Miroslav Suchý <msuchy(a)redhat.com> wrote:
>> Dne 8.9.2017 v 13:13 Neal Gompa napsal(a):
>>> No, I mean that you maintain mock source code and mock-core-configs
>>> source code in the same git repo, using tito to make independent
>>> releases. :(
>> * I do not need to run 'git grep' twice.
>> * when adding new option (both to config and code) it can be done in one atomic
>> * I still can `git blame` on files in new package and I get full history
>> * Thank to Tito the Source0 is just git-archive of that one directory and the
release process is still simple.
> Would you at least consider uploading tarballs into GitHub releases?
> It makes it easier for people who don't have tito to consume...
Is is so hard to install tito? I tried to follow
and it is quite long process...
this time, but I will not do that in future. I may add support to Tito as it can be
but doing that manually... no. :(
While *I* can on Fedora, I can't on Mageia (it crashes because DistGit
releaser isn't usable). In addition, not everyone has tito. Debian and
SUSE systems don't have tito. Mock is packaged on more distributions
than Fedora, and tito is rather Fedora-specific (to the point of being
mostly non-functional elsewhere).
I increasingly dislike the reliance on Tito because projects that use
it are often not able to be packaged in other distributions. We've
nearly killed all the usage of Tito in the DNF project because it
makes things really annoying for non Fedora consumers. It's only used
in dnf and dnf-plugins-core, and I hope we kill it there soon, too.
As a concept, tito isn't that bad. Other similar tools like
git-buildpackage-rpm (with some of the functionality merged in
upstream git-buildpackage) clearly show it's a desirable feature.
But tito makes life difficult for consumers that aren't on Fedora.
真実はいつも一つ！/ Always, there's only one truth!