On Tue Sep 20 05:59:20 2016, sprout wrote: > On Tue Sep 20 05:07:29 2016, davem wrote: > > How about we just don't bother keeping MANIFEST strictly sorted > > during > > development, (and so don't automatically test it for sortedness), and > > instead have it as an extra manual step in the release process ("step > > 97: > > run 'make manisort' and commit if MANIFEST has changed"). So it just > > gets > > done once per month and doesn't get in the way of everyone else. > > That makes sense. I was thinking of proposing that next if anyone > objected to a simple revert of the change. I have been wondering > since I started hacking on perl why we needed to keep it sorted > anyway. > > The best way to solve something that shouldn’t be a problem to begin > with is to remove the problem instead of working around it. > > > That does however leave open the issue of whether we should still > > automatically check for correctness (i.e. that MANFEST == git ls- > > files). > > manifest.t should continue to perform its other tests. Can the MANIFEST file be sorted via a git hook? -- Dez. --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=129229Thread Previous | Thread Next