Le samedi 30 novembre 2019 à 12:54 -0500, Neal Gompa a écrit : > On Sat, Nov 30, 2019 at 12:49 PM Miro Hrončok <mhroncok@xxxxxxxxxx> > wrote: > > On 30. 11. 19 17:26, Dominik 'Rathann' Mierzejewski wrote: > > > > > > 2. It would be useful if it generated the file list > > > automatically, too. > > > I had to drop .egg-info and .dist-info manually. > > It would. I don't know if we track this somewhere but it is > > certainly on our > > radar. Patrik (CCed) is working on it. > > > > I have done some API drafting and based on RPM limitations, we > > might end up with > > something like this: You have exemples of working implementations in go-rpm-macros and fonts-rpm-macros https://pagure.io/fonts-rpm-macros/ https://pagure.io/go-rpm-macros/ (see rpm/templates in those projects to look how the macros are used) Basically, you need to generate a set of rpm variables that contain at least the target subpackage name, and a way to deduce from it the filelist name (ideally, another clean rpm variable easy to manipulate) Then you just define a <foopkgfile> macro that generates the %file call for all <foopkg> variable sets. As long a you do it this way it’s fairly easy to manipulate the filelist in %build (or even %install) if the automated process made mistakes. But, generally, a well tested automated generation process will make less errors than a human toiling by rote. Regards, -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
