Samuel Sieb wrote: > On 4/28/20 1:06 PM, David wrote: >> What factors will play out by the person choosing to >> replace the current version of "bind" in the Rawhide >> repo" with a later version ? > > For rawhide, mostly just does it work and does it break > anything else. [...] >> And finally, what would happen in Fedora 32, for "bind" >> to get a point-relase update ? > > Successful testing in rawhide and generally no large > changes between versions. https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ is also relevant, as a more formal way of documenting the intended guidelines package maintainers should use when deciding when/if to update a given package in the various Fedora stages of release (e.g. Rawhide, or one of the current, stable releases). There's plenty of leeway and discretion for maintainers, so different packages and maintainers can and do vary a bit. >> Any helpful insights related to packaging procedures for >> newbies would be of interest. I have no clue what one >> does to compile a or build a package. > > That is a huge topic. Heh, now there's an understatement. ;) > I don't know where to start with that. I use "rpmbuild" > for my purposes, but I've seen it mentioned that "mock" is > the recommended way to build. Actual packages for Fedora > get built in koji. https://koji.fedoraproject.org/koji/ > There are a set of command line utilities for managing > packages and running builds. https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/ is one resource which might be useful to you David. -- Todd
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
