-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 After reading all responses in thread which is mentioned in subject I think we need to develop some policies / procedures how to deal with old cruft, for example: - - Requires: systemd-units - - Requires: /bin/mktemp Former has changed to systemd in guidelines X years ago (not sure when exactly, before I did my first package which contains systemd units, so I would guess something like 5-6 years ago). Latter was removed more then decade ago but we kept old Provides around for compatibility and seems after 10 years people still rely on them. Do you have ideas how policy / procedure of removal those should look like? - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlotDFMACgkQaVcUvRu8 X0yN2w//ZXwg9/bPRlBDSB7qe9dIEJEdJS4XAC1OdLGLDiscrCXjxhEj6HUpQ/nw Y0SQsICNs+QSsU2rggZ0n6w5DzWNU0CFPZbN73YfGnNvG8r6Tcv2Gy3zwKg8KwVq ihmr9HJwJvRpYs+ACwIIXZZUxhFnp4/ZM8skyqoN/V8TRBZiLqmaGozZ8xkkx8c/ 4R1PEXYxWgoIVAarV3JFo7SEqU2VXFjfHQXTsGfinHkgfpp5U5tRcUShFJDMlo8/ 90AtOXLd6wNh3pBTz9feM2PpAguQHXWDVFOWH+7dAlERZw6CeUmFMko0dqsR8UN7 6M/jOnXHO8eVRqKn8A41fXx1TeMoRsjHHSd2D+fb3ghHNzLKHX0fxphZJwgdGYce 1c00DoguOl7WIPRzIL+yrdNF3DbJeRTUhN4/ch+T5M08itOLQSDWxGDxbdfOxwNs 55pNHrD7QaupZjLox3zOZag5Uq378ZK80mwp0pochl0xBQ3L1xQLuBOEcye7Sh6+ niwQF/oMFn0y6F59N0arYi9d6Izg53Zf7FeZUuiiZDC93Uf9ifdZC6hLwjlZUToa 8Kf2tiSQI75WuUXZdUhTbeQJ8JNExxCSy6275KPbU4fB7hTd7tRkr/SclRek1ifz pGU4xIyC3cu5h1XlfgvTp/zeKS69x3ZimI7ZtdN37nbhlzwRc7I= =XP3c -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
