Hello Michael, I would agree with that. Just like it would be silly to ship the generated .o files in a source package.
I think that, given that valac is a compiler like any other, the generated .c files should not be part of the dist tarball. Instead should the build-dependencies include a specified version of valac. My personal recommendation would be, to all upstream packages, not to include generated .c files to the make-dist tarball. Before I guess it was needed, because valac was not considered a truthful real dependency. But nowadays it is. It is a compiler like any other. What files it generates should be of no concern to the packagers (in my opinion), just like .o files: the packager wants the resulting .pc, .a and .so files. Those files are more or less the same for vala sources. I added Jürg in CC to comment on this. Kind regards, Philip On Sun, 2017-04-09 at 19:34 +0200, Michael Biebl wrote: > 2017-04-09 19:31 GMT+02:00 Philip Van Hoof <phi...@codeminded.be>: > > I wonder if removing those .stamp files should be part of any > > make-target that is ~ standard for packaging tooling? In my opinion > > should such generated .c files share the rules of .o files. > > Well, that would defeat the point of shipping the generated .c files > in the dist tarball in the first place, no?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
