Subject: Re: New pkg submit: pkgsrc/sysutils/logrotate
To: Thomas Klausner <email@example.com>
From: Brian A. Seklecki <firstname.lastname@example.org>
Date: 08/06/2003 09:50:11
On Wed, 2003-08-06 at 08:00, Thomas Klausner wrote:
> On Wed, Aug 06, 2003 at 07:19:21AM -0400, Brian A. Seklecki wrote:
> > I have another package I'm working on that needs to depend on another
> > package:
> > pkgsrc/lang/tcl-expect
> > ...but that pkgsrc entry doesn't have a buildlink2.mk entry.
> Buildlink2.mk files are, in general, just for libraries and
> corresponding header files.
...which tcl-expect has (says the PLIST). However, without looking at
the GNU autoconf, I'm not sure if it check exclusively for the expect
binary in $PATH, or the libs and headers too.
The other two packages I need to depend on, GNUPG and mgetty+sendfax, do
not have libs and headers, and I can DEPENDS+= them, but tcl-expect is
I will check, but thanks for clearing that up.
Also, I see the OpenSSL buildlink2.mk is spitting out a "notice" message
when included. I want to do something like that with this new package
to let the user know that they can affect what features are build (and
associated pkgsrc dependencies created) by setting some environmental
variables in their shell before building
I didn't see an equivilant to MESSAGE for pre-builds, so I was just
going to do:
...is that acceptable?
> For all other uses, plain DEPENDS or BUILD_DEPENDS is good enough.
NOTE: When replying to a mailing list post, please be sure to reply to
the /list/ and cc: or bcc: myself as I am unable to promise a timely