This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: to-do: formalize/automate tracking of files maintained elsewhere
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: "GNU C. Library" <libc-alpha at sourceware dot org>
- Date: Wed, 25 Sep 2013 14:50:27 -0700 (PDT)
- Subject: Re: to-do: formalize/automate tracking of files maintained elsewhere
- Authentication-results: sourceware.org; auth=none
- References: <20130925202541 dot 3AD6F2C07C at topped-with-meat dot com> <Pine dot LNX dot 4 dot 64 dot 1309252126370 dot 31429 at digraph dot polyomino dot org dot uk>
> <https://sourceware.org/glibc/wiki/Regeneration> is intended to cover all
> cases of checked-in files not maintained as source in glibc (whether files
> that come verbatim from upstream source, or generated files).
Thanks for the pointer. The two categories are quite different and it is
unhelpful to conflate them. Generated files are pretty well dealt with by
the build system. Copied files are not dealt with by anything but people
happening to remember to manually do something. The task I requested is to
achieve a codified procedure (at least codified, if not mostly automated)
to ensure that copied files are not forgotten.
> Note that scripts/update-copyrights has its own list, used to avoid
> modifying copyright dates in such files.
Duplication of such lists is also unhelpful. Part of the
codification/automation task should be to move the list of copied files
into a single place that is used both by the new automation code and by
your script.
Incidentally, that script would do better to use 'git ls-files' rather than
find.
Thanks,
Roland