Closed shr-project closed 4 years ago
Drop this and what follows. I don't see how showing how different the recipes are helps further explain the need for the change.
I disagree, It shows why it's important to implement this change.
I disagree, It shows why it's important to implement this change.
Wouldn't still be important to implement it even if the recipes were identical?
Wouldn't still be important to implement it even if the recipes were identical?
No it wouldn't be important, because bitbake doesn't care from which directory the recipe was used, but when the built output is very different, then it's important to use the new recipe.
even if the recipes were identical
Actually, if a recipe moves to a different subdirectory, it's ROS_CN
setting will be different, so the recipes will never be identical.
I don't see how showing how different the recipes
I disagree, It shows why it's important to implement this change.
The details of the differences are unimportant, so perhaps show how different they are by piping the diff
output into diffstat
? (Use diff -C 1
so that the filename appears in the diffstat
output.)
Comments explaining what would cause unexpected output from git status --porcelain and glob.
Can you please provide these comments?
I don't know what unexpected might have happen especially in combination with --only which isn't implemented yet AFAIK.
I don't know what unexpected might have happen especially in combination with --only which isn't implemented yet AFAIK.
If it's unexpected, shouldn't it be considered an ASSERT that stops execution?
The output is verbose, but err() output is quite rare in it and contains even more important messages than this unexpected output, see the errors in last meta-ros regeneration: http://paste.ubuntu.com/p/b6JbJyTp8d/
OK, then let's leave it as is.
@allenh1 < Now that this last open PR was been merged, could you release a v0.3.2 ?
@herb-kuta-lge That sounds like a good idea to me!
@tfoote FYI
the overlay.repo.remove_file(existing, True) call in bitbake/genpackages.py works fine, but only when the new recipe is being generated in the same directory as the previous version: existing = glob.glob('{}*.bb'.format(prefix)) where prefix is: prefix = '{0}/meta-ros{1}-{2}/generated-recipes/{3}/{4}' which will result in multiple recipes for the same package when the package is moved to different prefix like pcl-conversions did for dashing and eloquent:
and especially for dashing where the version is identical it's undeterministic which recipe bitbake will use. And the recipe wasn't just moved to different directory, it's quite different:
grep in the current build logs shows that the "older" meta-ros2-dashing/generated-recipes/pcl-conversions/pcl-conversions_2.0.0-1.bb was currently being used in dashing instead of "newer" meta-ros2-dashing/generated-recipes/perception-pcl/pcl-conversions_2.0.0-1.bb
corresponding rosdistro change for dashing: https://github.com/ros/rosdistro/commit/19b06c44df69f9bf44dd7ab1b74236e9e386c848 and eloquent: https://github.com/ros/rosdistro/commit/67c3ef53979ea8d85254bdfc427b142eda69fb57
Signed-off-by: Martin Jansa martin.jansa@lge.com