dependency artifacts for faster builds/gerrit-verifications

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Max msuraev at sysmocom.de
Fri May 5 15:58:03 UTC 2017


On 05.05.2017 17:48, André Boddenberg wrote:
>
> How would you extract information about dependencies from configure.ac?

PKG_CHECK_MODULES() entries should be good enough. There's probably some autotools
trick I don't know which would allow to get those automatically without grepping
through. Alternatively one can look in debian/control for Build-Depends entries. Not
sure if Debian got any dh_* which could extract this in a nice way.

> I would probably curl
> http://git.osmocom.org/${project}/plain/contrib/jenkins.sh and
> grep+cut all strings occurring after osmo-build-dep.sh and recursively
> do the same for all found dependencies.
>
> Do you in general think an automated way of creating dotty dependency
> graph would be nice to have?
I wouldn't bother just for dotty. Having dependencies part of jenkins jobs to be
autogenerated would be kinda cool but:
- not sure if it's not overengineering: dependencies do not change that often

- not sure how many false positives/negatives the approaches above give

-- 
Max Suraev <msuraev at sysmocom.de> http://www.sysmocom.de/
======================================================================= 
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93 
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B 
* Geschaeftsfuehrer / Managing Director: Harald Welte 







More information about the OpenBSC mailing list