Home Original page

[Python-Dev] End of the mystery "@README.txt Mercurial bug"

Eric V. Smith eric at trueblade.com
Wed Jun 26 15:04:49 CEST 2013 
On 6/26/2013 8:57 AM, Ronald Oussoren wrote:
> 
> On 26 Jun, 2013, at 14:18, Eric V. Smith <eric at trueblade.com> wrote:
> 
>> On 6/26/2013 6:43 AM, a.cavallo at cavallinux.eu wrote:
>>> .. or having hg "purging" unwanted build artifact (probably cleaning up
>>> the .hgignore file first)
>>
>> How would that work? How could hg purge the .bak, .orig, .rej, .old,
>> etc. files?
>>
>>>>> find $(srcdir)/* ...
>>>>>
>>>>> to avoid this problem. It won't expand the .hg top-level directory.
>>>>
>>>>   Or find \( -type d -name .hg -prune \) -o ...
>>
>> I'm torn. Yours is more obvious, but we'd likely need to add .svn, .git,
>> etc. Maybe find $(srcdir)/[a-zA-Z]* ... would be good enough to ignore
>> all dot directories/files?
> 
> Is the find command in the distclean target still needed? The comment for the distclean target says it is used to clean up the tree for distribution, but that's easier to accomplish by using a clean checkout.
> 
> The target is still useful to get a clean tree when you're building with srcdir == builddir, but you don't need the find command for that.

I run 'make distclean' fairly often, but maybe it's just out of habit.
If I'm adding/deleting modules, I want to make sure there are no build
artifacts. And since I have modified files, a clean checkout won't help
(easily, at least).

But me running distclean is not the same as answering your question
about the find command being needed, I realize.

-- 
Eric.
More information about the Python-Dev mailing list