Le jeudi 01 novembre 2018 à 13:36 +0100, Iñaki Ucar a écrit : Hi,
> - Arch, Requires, BuildRequires, libdir/datadir: As Elliott pointed > out already, archful packages can be detected just by looking into the > DESCRIPTION file, by checking whether the NeedsCompilation flag > exists. If it does, the package must go to libdir and R-devel must be > added as BuildRequires. Furthermore, the LinkingTo field in the > DESCRIPTION file lists packages that must be added as BuildRequires, And that makes it yet another language that needs https://github.com/rpm-software-management/rpm/issues/104 and the functional part of https://pagure.io/fesco/issue/2004 to be automated properly. > %files are pretty > standard: there is a basic set, and then other may or may not be > there, such as LICENSE/LICENCE, NEWS/NEWS.md, README/README.md, > Changelog, and CITATION; and directories such as libs and include. Take a look at https://copr.fedorainfracloud.org/coprs/nim/fontpackages-2/builds/ for an example on how to pass doc wildcards to generic automation macros. (currently polishing it and cross-pollinating with go macros) Regards, -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
