mark at geekhive
Feb 19, 2002, 12:58 AM
Post #3 of 4
(873 views)
Permalink
|
|
Re: [Bricolage-Devel] Re: [Bricolage-Commits] Added reminder that missing libapreq version is for a reason.
[In reply to]
|
|
David Wheeler wrote:
>
> On Fri, 2002-02-15 at 10:27, Mark Jaroski wrote:
> > Log Message:
> > -----------
> > Added reminder that missing libapreq version is for a reason.
>
> I hope you mean that you're detecting the presence of libapreq, just not
> of a particular version, right? Most of the modules we require do not
> require a particular version. See the README in Bundle::Bricolage.
Yes, that's exactly what's happening. The module script
takes the version from your pod file, but unfortunately
libapreq has no version info, so I can't check for it.
Instead the script inserts a blank for it's version so that
the m4 macro doesn't go looking for a version.
What I added here, if you look at the diff, is a paragraph
long comment explaining this. It didn't make much sense to
me to duplicate that in the commit message sinse you can
just read down.
--
--
=================================================================
-- mark at geekhive dot net --
_______________________________________________
Bricolage-Devel mailing list
Bricolage-Devel [at] lists
https://lists.sourceforge.net/lists/listinfo/bricolage-devel
|
