--nextPart1415910.M1jntsyBdO
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Tuesday 09 July 2013 06:33:21 Scott Kitterman wrote:
> On Tuesday, July 09, 2013 12:05:30 PM =C3=80lex 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) =
file.
> > > 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 inste=
ad 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 somethi=
ng out.
> >=20
> > Our projects are a mess when it comes to runtime dependencies, why =
don't
> > we
> > fix that for example?
>=20
> How would a run time only dependency be expressed?  I've seen some pe=
ople
> put them in find_package, which is wrong and then we end up having to=
 patch
> it away.
>=20
> For build-time dependencies, particularly determining minimum version=

> requirements, I end up reading CMakeLists.txt in my favorite editor. =
 That's
> not ideal either.
what about having this information available in a standardized format, =
e.g. a=20
dependencies.xml?

Cheers
Martin
--nextPart1415910.M1jntsyBdO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iEYEABECAAYFAlHb6EUACgkQqVXwidMiVrruEwCeK+ivnvLIMznaW8K1A0fP/d1G
tIMAoI/V2m2kYvX7ZpFrXtu3KuyFC56n
=skdO
-----END PGP SIGNATURE-----

--nextPart1415910.M1jntsyBdO--