> On 14 Mar 2019, at 23:57, Felix Schwarz wrote:
>
>
> Am 14.03.19 um 13:08 schrieb Fabio Valentini:
>> I think there is (or at least, there used to be) a section in the packaging
>> guidelines which explicitly mentions that including both .c and .h files in
>> non-devel packages is fine (and
Am 14.03.19 um 13:08 schrieb Fabio Valentini:
> I think there is (or at least, there used to be) a section in the packaging
> guidelines which explicitly mentions that including both .c and .h files in
> non-devel packages is fine (and indeed, expected) for compilers and build
> tools which need t
On Thu, Mar 14, 2019, 10:19 Dan Čermák
wrote:
> Hi Christophe,
>
> since the .c files appear to be fundamental for the functionality of
> make-it-quick, I'd rather silence this one specific check via an
> rpmlintrc file instead of renaming them or converting this into a -devel
> package.
>
> Rena
Hi Christophe,
since the .c files appear to be fundamental for the functionality of
make-it-quick, I'd rather silence this one specific check via an
rpmlintrc file instead of renaming them or converting this into a -devel
package.
Renaming them is probably a lot more work and calling it -devel wi
Hello,
I’m currently working on a Fedora package for make-it-quick
(https://github.com/c3d/make-it-quick), a make-only build system with basic
auto-configuration.
rpmlint complains about shipping .c files in a non -devel package. The package
does contains several small .c files that are used
