[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2004Q4 2004-10-03T00:12:51Z 2004-10-03T00:12:51Z tv tv 2004-10-03T00:12:51Z urn:sha1:b5510d5a2d7f9a1406603d922ae5d8548950233c 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-22T08:09:14Z jlam jlam 2004-09-22T08:09:14Z urn:sha1:08039266e343e3cb99feb5cbfd5fd9acf006ac97 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-05-07T01:14:46Z xtraeme xtraeme 2004-05-07T01:14:46Z urn:sha1:c2b49ba19c5c2978d0a18385dfdf1409aa9ce0cc all these packages. 2004-03-18T09:12:08Z jlam jlam 2004-03-18T09:12:08Z urn:sha1:847385cb2d9851c0ea2e94e51e8cb05abfdd6dbf by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES. 2004-03-05T19:25:06Z jlam jlam 2004-03-05T19:25:06Z urn:sha1:12109d5b873e13ef999184b4ace84a18e0a72358 buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk. 2004-02-27T07:56:33Z xtraeme xtraeme 2004-02-27T07:56:33Z urn:sha1:47ad28d5415815e07fb921a5d9331bd817283e9d 2004-02-14T17:21:32Z jlam jlam 2004-02-14T17:21:32Z urn:sha1:c46da24c142eef5eab634a945d7e1d201115cb8b relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk. 2004-01-20T12:07:06Z agc agc 2004-01-20T12:07:06Z urn:sha1:0bc53217fe50327f0f59e7136db15f92f75951d9 2004-01-03T18:49:33Z reed reed 2004-01-03T18:49:33Z urn:sha1:a06f12bdce16b588525a769c9f6a99518e6aaef5 Tiff is backward compatible, but was broken on amd64 platform so this makes sure new tiff is used. 2003-12-03T19:00:02Z xtraeme xtraeme 2003-12-03T19:00:02Z urn:sha1:e91d6a42fc041f79dabcbf60fc49ea6dda512668 Developer's Image Library (DevIL) is a programmer's library to develop applications with very powerful image loading capabilities, yet is easy for a developer to learn and use. Ultimate control of images is left to the developer, so unnecessary conversions, etc. are not performed. DevIL utilizes a simple, yet powerful, syntax. DevIL can load, save, convert, manipulate, filter and display a wide variety of image formats. Currently, DevIL can load .bmp, .cut, .dds, .doom, .gif, .ico, .jpg, .lbm, .mdl, .mng, .pal, .pbm, .pcd, .pcx, .pgm, .pic, .png, .ppm, .psd, .psp, .raw, .sgi, .tga and .tif files. Formats supported for saving include .bmp, .dds, .h, .jpg, .pal, .pbm, .pcx, .pgm,.png, .ppm, .raw, .sgi, .tga and .tif. DevIL currently supports the following APIs for display: OpenGL, Windows GDI, SDL, DirectX and Allegro. Compilers that can compile DevIL or use it include Djgpp, MSVC++, Linux gcc, Delphi, Visual Basic, Power Basic and Dev-C++.