On Tuesday, July 09, 2013 12:05:30 PM =C0lex Fiestas wrote:
> On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
> > We don't just run a sed rule on each spec (pkgbuild, in my case) fi=
le. We
> > check for new dependencies (resp. dependencies not needed anymore),=
 new
> > modules (resp. modules not part of the SC anymore), build failure, =
etc...
>=20
> Can't we do something so you don't have to hunt this down but instead=
 just
> read a list?
>=20
> For build time dependencies, we could do something by looking for
> find_package, and for runtime dependencies we should figure something=
 out.
>=20
> Our projects are a mess when it comes to runtime dependencies, why do=
n't we
> fix that for example?

How would a run time only dependency be expressed?  I've seen some peop=
le put=20
them in find_package, which is wrong and then we end up having to patch=
 it=20
away.

For build-time dependencies, particularly determining minimum version=20=

requirements, I end up reading CMakeLists.txt in my favorite editor.  T=
hat's=20
not ideal either.

Scott K