Comments (9)
I am wondering if it is necessary / useful to update all the packages which don't have any metadata or if we should just close those and let them keep adding plain str
dependency names?
from colcon-core.
I think they can be closed for now, and if at some point those packages want to add metadata then that can be done in a PR with the metadata addition.
Do you think the guidance from now on should be to use DependencyDescriptor?
Should consumers of dependencies that need the metadata just always verify the dependency is a DependencyDescriptor?
from colcon-core.
I think they can be closed for now, and if at some point those packages want to add metadata then that can be done in a PR with the metadata addition.
Sounds good to me. Please go ahead and close the ones which don't contain metadata atm (or update them to do so).
Should consumers of dependencies that need the metadata just always verify the dependency is a DependencyDescriptor?
Atm they certainly have to do that before trying to access the metadata
attribute.
Do you think the guidance from now on should be to use DependencyDescriptor?
Since code will need to check for the foreseeable future anyway if the entry is a descriptor or a plain str
I wouldn't force code to be updated. Maybe in future minor release before reaching 1.0 it would be good to "break" the assumption and require every entry to be a descriptor.
from colcon-core.
Closed all the changes that don't add any metadata. Do you know when you'll cut the next release of colcon-core?
from colcon-core.
We recently changed our bootstrap repo which contains all the Python packages so I am not 100% confident to do it now (with others not available) if something goes wrong. But I will aim to ship a new release of colcon-core
on Monday.
from colcon-core.
I am still blocked by problems with our bootstrap repo. I will comment here as soon as I was able to do a release... 😞
from colcon-core.
colcon-core
0.3.10 has just been released. Sorry for the delay. Please update the remaining PRs to include that version dependency - their CI should then pass and be mergable.
from colcon-core.
Also colcon-python-setup-py
0.2.1 and colcon-ros
0.3.5 have been 🚢.
Is there anything else remaining in the scope of this ticket?
from colcon-core.
Awesome, thanks for getting these changes shipped! Everything for this ticket is completed. Will close it.
from colcon-core.
Related Issues (20)
- Cache get_extension_points output
- empy version incompatibility HOT 4
- [Question] Correct way to build a ros driver which depends on a library without having to run 'sudo make install' on the library. HOT 6
- Design intent of setup.sh vs setup.bash HOT 4
- Why can data_files destinations not be absolute for ament_python packages? HOT 4
- [Question] Recommended way to invoke colcon on ubuntu noble? / request for release recent colcon in ROS APT ubuntu noble repos HOT 2
- Feature Request: Multiple `build-base` and `install-base` for multiple `base-paths`
- Colcon hangs when stdout / stderr is redirected and output line is longer than default buffer size HOT 2
- Colcon extends LD_LIBARAY_PATH with cross compiled libraries HOT 4
- Package includes directory has subdir of subdir of package name HOT 1
- Install colcon on x86 to cross compile ros2 HOT 4
- Error building after deleting a file: can't copy '<deleted-file> doesn't exist or not a regular file HOT 3
- colcon list Traceback (most recent call last): File "/usr/bin/colcon", line 33, in <module> sys.exit(load_entry_point('colcon-core==0.16.0', 'console_scripts', 'colcon')()) File "/usr/lib/python3/dist-packages/colcon_core/command.py", line 118, in main return _main(command_name=command_name, argv=argv) File "/usr/lib/python3/dist-packages/colcon_core/command.py", line 185, in _main create_log_path(args.verb_name) File "/usr/lib/python3/dist-packages/colcon_core/location.py", line 186, in create_log_path os.makedirs(str(path)) File "/usr/lib/python3.10/os.py", line 225, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: 'log/list_2024-04-06_02-45-22' HOT 3
- colcon returns with success when extension loading fails
- No executable found for scripts when using --symlink-install and install(PROGRAMS) HOT 3
- Torch shared library: libc10.so: cannot open shared object file HOT 4
- Several lines from _local_setup_util_sh.py contain this: E501 line too long
- Request to transfer `colcon-lint` extension repository
- `colcon build` executor not affecting `make -j` command HOT 1
- Distinguish between required and optional dependencies HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from colcon-core.