[mythtv] Problem with build process - python metadata files
mythtv at love2code.net
Mon Jan 25 19:24:59 UTC 2021
On Thu, 2021-01-21 at 11:31 -0500, Peter Bennett wrote:
> Hi David
> Since you are more familiar with this, perhaps you can look into it.
> I think it may be related to the "obj" directory changes you made
> some time back.
This was introduced last January with the changes to rewrite python
files to explicitly use the currently installed python executable.
> When I make mythtv and install, tmdb3.py is installed in
> If I make some changes to tmdb3.py, make and install again, I get
> usr/share/mythtv/metadata/Movie/tmdb3.py [out of date file]
> usr/share/mythtv/metadata/Movie/Movie/tmdb3.py [new file]
The problem is with the way these rewrite rules are using a recursive
copy command. The command "cp -r foo obj/foo" works every time if the
destination doesn't exist or if "foo" is a file. However, if "foo" is a
directory the first time you run the command you create the directory
"obj/foo" and all subsequent times you create "obj/foo/foo". Exactly
what you're seeing.
I should have a fix committed soon.
> The system will run the out of date file since that is where it
> to find tmdb3.py.
> In the source directory structure is a similar thing after the make
> [source file I am changing]
> [more recent copy of file]
> [out of date file]
> The same problem may exist with other files.
More information about the mythtv-dev