Dependencies

Dependencies

[Alex Elder]

I occasionally bump into newly-required packages when I'm trying
to build ceph.  I don't remember what they have been, but today I
hit this when I tried "make clean":

     configure: error: --with-radosgw was given but libcurl (libcurl-dev 
on debian) not found

That was resolved by installing libcurl4-gnutls-dev (at least I
think that's what made it go away).

After that I hit this:

     configure: error: --with-gtk2 was given, but test for gtkmm failed

That took a number of trials, but eventually I think the package
that I installed which made this problem go away was libgtkmm-2.4-dev.

Is there any way that we can do any or all of these?
- we can identify when a new dependency like that has been added
- we can do this automatically
- we can mention something (like in a release announcement) when
   new dependencies have been added since last time
- we can do a nicer job of telling the user that a particular
   package is missing--better than the "test for gtmm failed" kind
   of message that the configure script provides

					-Alex

Re: Dependencies

[Tommi Virtanen]

[Resending to ceph-devel without the HTML gmail put in.]

On Mon, Mar 5, 2012 at 07:46, Alex Elder <elder@dreamhost.com> wrote:
>
> Is there any way that we can do any or all of these?
> - we can identify when a new dependency like that has been added

The Build-Depends: line in debian/control changed. Or, the
BuildRequires: lines in ceph.spec.in changed, for RPM dstros.

(Or someone screwed up, and forgot to change them, but when that gets
fixed, go back to previous paragraph.)

> - we can do this automatically
> - we can mention something (like in a release announcement) when
>  new dependencies have been added since last time

Automatically answering whether that content changed after last
release is easy. Release management is not (it's a repetitive,
relatively rare & high-importance task).

> - we can do a nicer job of telling the user that a particular
>  package is missing--better than the "test for gtmm failed" kind
>  of message that the configure script provides

That's autoconf, it's hard to improve on, and intentionally does not
assume the system is managed using debs or RPM etc.

As long as you're on Debian/Ubuntu, running dpkg-checkbuilddeps will
check your system against debian/control.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html