Next | Query returned 147 messages, browsing 81 to 90 | Previous

History of commit frequency

CVS Commit History:


   2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908)
Log message:
Libtool fix for PR pkg/26633, and other issues.  Update libtool to 1.5.10
in the process.  (More information on tech-pkg.)

Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.

Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
   2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703)
Log message:
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:

	lib/libfoo.a
	lib/libfoo.la
	lib/libfoo.so
	lib/libfoo.so.0
	lib/libfoo.so.0.1

one simply needs:

	lib/libfoo.la

and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.

Also make LIBTOOLIZE_PLIST default to "yes".
   2004-08-31 21:24:42 by Jeremy C. Reed | Files touched by this commit (1)
Log message:
Move including the ../../mk/bsd.prefs.mk and checking for Linux
to after GNU_CONFIGURE and USE_LIBTOOL being set.
This fixes the problem where the lt_cv_sys_max_cmd_len was not
added to the CONFIGURE_ENV.

Now that I think about it, I caused this problem when I added that
Linux check...
   2004-08-28 08:05:32 by Johnny C. Lam | Files touched by this commit (25)
Log message:
Use the new BUILDLINK_TRANSFORM commands to more precisely state the
intended transformation: use "rm" to remove an option, \ 
"rmdir" to remove
all options containing a path starting with a given directory name, and
"rename" to rename options to something else.
   2004-07-04 11:55:19 by Thomas Klausner | Files touched by this commit (4)
Log message:
Unused.
   2004-06-04 07:25:39 by Jeremy C. Reed | Files touched by this commit (1)
Log message:
Fail if this package is to be built under Linux.  This is normal
for Linux. Most (all?) Linux distros don't provide a libiconv
package, because GLIBC's iconv support is good enough.

At this time, using PKG_FAIL_REASON instead of PKG_SKIP_REASON
so we can catch examples of packages depending on this.

The builtin.mk was improved to help stop it from being used under
Linux.

This was okayed by Rene Hexel, the maintainer.

Todo: fix abiword build because it should not require this libiconv
package under Linux.
   2004-06-04 07:21:14 by Jeremy C. Reed | Files touched by this commit (1)
Log message:
By default, assume that the native iconv on Linux systems using
GLIBC supports GNU libiconv's API. So don't depend on pkgsrc's
libiconv for it. This is normal: most other Linux distros don't
provide a libiconv package.

This was discussed on tech-pkg list over past two months. It has
helped a few users under Linux where they had some problems with
conflicts with their working iconv() support provided with libc
and the libiconv package.

This was okayed by maintainer, Rene Hexel.

This still needs some improvement. Some packages still try to
force libiconv usage even though not needed.
   2004-05-20 18:13:05 by Dan Winship | Files touched by this commit (2)
Log message:
Revert the change to put -liconv into BUILDLINK_LDFLAGS.iconv (which
breaks some things on Darwin) and fix audio/musicpd so it doesn't need
it (by faking out a configure check that gets confused by the
iconv_open -> libiconv_open renaming)
   2004-05-17 23:32:35 by Stoned Elipot | Files touched by this commit (26)
Log message:
Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymore
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
   2004-05-03 04:22:24 by Soren Jacobsen | Files touched by this commit (1)
Log message:
Add ${BUILDLINK_LDADD.iconv} to BUILDLINK_LDFLAGS.iconv.

Next | Query returned 147 messages, browsing 81 to 90 | Previous