Thank you all for the replies and interest. It'd be great to have many co-maintainers. I think the best (only?) way to do this is to add people after the package has gone through review and been approved. On Mon, Nov 27, 2023 at 07:58:18AM +0000, Piotr Szubiakowski wrote: > Hey! > > I would be happy to help package Nix on Fedora. I prepared a SPEC[1] some time ago. > > > The issue I hit was building documentation. It depends on > mdBook[2]. Without documentation manual and `nix-env --help` doesn't > work. I don't think that packaging the docs is a hard requirement. The manual is online and I'm sure that many people would view it there, even if we provided a local copy. 'nix-env --help' not working is a bummer, but I don't think it's a blocker either. I looked [1], and I see some differences in packaging: - I opted to put the libraries in /usr/lib64/nix/ and retain the RUNPATH so that they get loaded from there. My thinking was that the libraries are "private", i.e. they are used by the nix binaries and nothing else. But I see that you have a -devel subpackage… Is it actually useful for anything? (If there is no known user, then I'd prefer to not add the -devel package initially. If it turns out to be useful later on, it can always be added.) - for the users, I'd prefer to create a sysusers file and submit it upstream. - I see you have aws-sdk-cpp-devel. The build seemed to work fine without. - I see you have '%undefine _hardened_build'. I didn't see any issues without that… Maybe it's not needed anymore? Zbyszek -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
