Message ID | 20250723163258.548756-2-Rauch.Christian@gmx.de |
---|---|
State | New |
Headers | show |
Series |
|
Related | show |
Quoting Christian Rauch (2025-07-23 17:32:57) > This metadata file provides meta information about the version, licence, > maintainers and build dependencies. The file is used by build systems, such > as colcon, to manage and resolve build dependencies. > > The file structure is defined at: https://www.ros.org/reps/rep-0149.html > > Signed-off-by: Christian Rauch <Rauch.Christian@gmx.de> > Acked-by: Kieran Bingham <kieran.bingham@ideasonboard.com> > --- > package.xml | 44 ++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 44 insertions(+) > create mode 100644 package.xml > > diff --git a/package.xml b/package.xml > new file mode 100644 > index 000000000..29629ad12 > --- /dev/null > +++ b/package.xml > @@ -0,0 +1,44 @@ > +<?xml version="1.0"?> > +<!-- SPDX-License-Identifier: CC0-1.0 --> > +<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> > +<package format="3"> > + <name>libcamera</name> > + > + <version>0.5.1</version> > + > + <description>An open source camera stack and framework for Linux, Android, and ChromeOS</description> > + > + <maintainer email="Rauch.Christian@gmx.de">Christian Rauch</maintainer> Does this convey publicly that you are the official maintainer of libcamera completely? If this is a top level 'package.xml' in the upstream public repo ... It would be hard to identify that you are only the maintainer of 'this file' ? This topic seems ... tricky.... > + > + <license>Apache-2.0</license> > + <license>BSD-2-Clause</license> > + <license>BSD-3-Clause</license> > + <license>GPL-2.0-or-later</license> > + <license>LGPL-2.1-or-later</license> > + > + <url>https://libcamera.org</url> > + > + <author email="libcamera-devel@lists.libcamera.org">libcamera project</author> > + > + <buildtool_depend>meson</buildtool_depend> > + <buildtool_depend>pkg-config</buildtool_depend> > + <buildtool_depend>git</buildtool_depend> > + > + <build_depend>python3-yaml</build_depend> > + <build_depend>python3-ply</build_depend> > + <build_depend>python3-jinja2</build_depend> > + <build_depend>openssl</build_depend> > + <build_depend>pybind11-dev</build_depend> > + > + <depend>yaml</depend> > + <depend>libssl-dev</depend> > + <depend>libudev-dev</depend> > + <depend>python3</depend> > + > + <!-- workaround for https://bugs.libcamera.org/show_bug.cgi?id=189 --> > + <depend>libatomic</depend> > + > + <export> > + <build_type>meson</build_type> > + </export> > +</package> > -- > 2.43.0 >
Am 23.07.25 um 19:22 schrieb Kieran Bingham: > Quoting Christian Rauch (2025-07-23 17:32:57) >> This metadata file provides meta information about the version, licence, >> maintainers and build dependencies. The file is used by build systems, such >> as colcon, to manage and resolve build dependencies. >> >> The file structure is defined at: https://www.ros.org/reps/rep-0149.html >> >> Signed-off-by: Christian Rauch <Rauch.Christian@gmx.de> >> Acked-by: Kieran Bingham <kieran.bingham@ideasonboard.com> >> --- >> package.xml | 44 ++++++++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 44 insertions(+) >> create mode 100644 package.xml >> >> diff --git a/package.xml b/package.xml >> new file mode 100644 >> index 000000000..29629ad12 >> --- /dev/null >> +++ b/package.xml >> @@ -0,0 +1,44 @@ >> +<?xml version="1.0"?> >> +<!-- SPDX-License-Identifier: CC0-1.0 --> >> +<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> >> +<package format="3"> >> + <name>libcamera</name> >> + >> + <version>0.5.1</version> >> + >> + <description>An open source camera stack and framework for Linux, Android, and ChromeOS</description> >> + >> + <maintainer email="Rauch.Christian@gmx.de">Christian Rauch</maintainer> > > Does this convey publicly that you are the official maintainer of > libcamera completely? That means that I am the maintainer of the "libcamera" package and that I am the contact person regarding issues or requests related solely to the packaging of libcamera. A package can have multiple "maintainer" entries. See for example the "apriltag" library as a plain CMake project: https://github.com/AprilRobotics/apriltag/blob/master/package.xml I think this is similar to how other packages are maintained. E.g. the libcamera packages on Debian use a mailing list as point of contact: https://tracker.debian.org/pkg/libcamera and does not mention the authors as maintainer. > If this is a top level 'package.xml' in the upstream public repo ... > > It would be hard to identify that you are only the maintainer of 'this > file' ? We could of course add multiple people as maintainers, or even a "libcamera-package" mailing list or similar. That was my initial intention with adding Laurent as an additional maintainer. I could also add "libcamera-devel@lists.libcamera.org" as the sole maintainer. Up until now, I acted as the sole maintainer and did not receive any notifications, even when builds failed. So we could do that and change the maintainer from "libcamera-devel" back to something else if there are undesired notifications. > This topic seems ... tricky.... > >> + >> + <license>Apache-2.0</license> >> + <license>BSD-2-Clause</license> >> + <license>BSD-3-Clause</license> >> + <license>GPL-2.0-or-later</license> >> + <license>LGPL-2.1-or-later</license> >> + >> + <url>https://libcamera.org</url> >> + >> + <author email="libcamera-devel@lists.libcamera.org">libcamera project</author> >> + >> + <buildtool_depend>meson</buildtool_depend> >> + <buildtool_depend>pkg-config</buildtool_depend> >> + <buildtool_depend>git</buildtool_depend> >> + >> + <build_depend>python3-yaml</build_depend> >> + <build_depend>python3-ply</build_depend> >> + <build_depend>python3-jinja2</build_depend> >> + <build_depend>openssl</build_depend> >> + <build_depend>pybind11-dev</build_depend> >> + >> + <depend>yaml</depend> >> + <depend>libssl-dev</depend> >> + <depend>libudev-dev</depend> >> + <depend>python3</depend> >> + >> + <!-- workaround for https://bugs.libcamera.org/show_bug.cgi?id=189 --> >> + <depend>libatomic</depend> >> + >> + <export> >> + <build_type>meson</build_type> >> + </export> >> +</package> >> -- >> 2.43.0 >>
diff --git a/package.xml b/package.xml new file mode 100644 index 000000000..29629ad12 --- /dev/null +++ b/package.xml @@ -0,0 +1,44 @@ +<?xml version="1.0"?> +<!-- SPDX-License-Identifier: CC0-1.0 --> +<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?> +<package format="3"> + <name>libcamera</name> + + <version>0.5.1</version> + + <description>An open source camera stack and framework for Linux, Android, and ChromeOS</description> + + <maintainer email="Rauch.Christian@gmx.de">Christian Rauch</maintainer> + + <license>Apache-2.0</license> + <license>BSD-2-Clause</license> + <license>BSD-3-Clause</license> + <license>GPL-2.0-or-later</license> + <license>LGPL-2.1-or-later</license> + + <url>https://libcamera.org</url> + + <author email="libcamera-devel@lists.libcamera.org">libcamera project</author> + + <buildtool_depend>meson</buildtool_depend> + <buildtool_depend>pkg-config</buildtool_depend> + <buildtool_depend>git</buildtool_depend> + + <build_depend>python3-yaml</build_depend> + <build_depend>python3-ply</build_depend> + <build_depend>python3-jinja2</build_depend> + <build_depend>openssl</build_depend> + <build_depend>pybind11-dev</build_depend> + + <depend>yaml</depend> + <depend>libssl-dev</depend> + <depend>libudev-dev</depend> + <depend>python3</depend> + + <!-- workaround for https://bugs.libcamera.org/show_bug.cgi?id=189 --> + <depend>libatomic</depend> + + <export> + <build_type>meson</build_type> + </export> +</package>