[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=cube-native-xorg 2008-03-03T19:21:37Z 2008-03-03T19:21:37Z jlam jlam@pkgsrc.org 2008-03-03T19:21:37Z urn:sha1:0bb78c6c9d3855e92497417696475484322d451c their files via a custom do-install target. 2007-07-31T14:44:02Z obache obache@pkgsrc.org 2007-07-31T14:44:02Z urn:sha1:8427aa0d23853b8f8b3da5cf51f9861b53ad73f7 Almost of patches are inspired by emulators/vmware-module3. 2007-02-22T19:26:05Z wiz wiz@pkgsrc.org 2007-02-22T19:26:05Z urn:sha1:601583c3207bd23bb05d0761888aefcb5699e1c2 Patch provided by Sergey Svishchev in private mail. 2007-01-31T00:04:11Z wiz wiz@pkgsrc.org 2007-01-31T00:04:11Z urn:sha1:29abbd1c1be1e6720eb67dd91033a7fbcd742ce1 ftp://asim.lip6.fr/outgoing/packages/i386/3.1/20070114.1132/broken.html (latest 3.1/i386 bulk build of 2006Q4). Feel free to fix them... 2006-07-05T06:53:12Z jlam jlam@pkgsrc.org 2006-07-05T06:53:12Z urn:sha1:3ba41e8b0cf81719575381c547a3ec3f4987b846 variables so that the default INSTALL/DEINSTALL scripts from the pkginstall framework do the right thing. Where possible, move some post-install directions for package setup into MESSAGE files so that they may be re-inspected by querying the installed package using "pkg_info -D ...". 2006-05-18T20:29:58Z wiz wiz@pkgsrc.org 2006-05-18T20:29:58Z urn:sha1:991dcdf97831205f87804d4d9524bc57a4e9caa8 ftp://ftp.NetBSD.org/pub/pkgsrc/misc/kristerw/pkgstat/i386-3.0/20060501.1050/broken.html 2006-03-14T01:14:26Z jlam jlam@pkgsrc.org 2006-03-14T01:14:26Z urn:sha1:daad0f3d6ce8b344ce91e35e98ea05abf8e03f2d INSTALL/DEINSTALL script creation within pkgsrc. If an INSTALL or DEINSTALL script is found in the package directory, it is automatically used as a template for the pkginstall-generated scripts. If instead, they should be used simply as the full scripts, then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC explicitly, e.g.: INSTALL_SRC= ${PKGDIR}/INSTALL DEINSTALL_SRC= # emtpy As part of the restructuring of the pkginstall framework internals, we now *always* generate temporary INSTALL or DEINSTALL scripts. By comparing these temporary scripts with minimal INSTALL/DEINSTALL scripts formed from only the base templates, we determine whether or not the INSTALL/DEINSTALL scripts are actually needed by the package (see the generate-install-scripts target in bsd.pkginstall.mk). In addition, more variables in the framework have been made private. The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are more sensible names given the very few exported variables in this framework. The only public variables relating to the templates are: INSTALL_SRC INSTALL_TEMPLATE DEINSTALL_SRC DEINSTALL_TEMPLATE HEADER_TEMPLATE The packages in pkgsrc have been modified to reflect the changes in the pkginstall framework. 2006-03-04T21:28:51Z jlam jlam@pkgsrc.org 2006-03-04T21:28:51Z urn:sha1:9c8b5ede437e0b7c2f7b0cdd5f8500d619968fdb developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers. 2006-01-04T04:29:05Z schmonz schmonz@pkgsrc.org 2006-01-04T04:29:05Z urn:sha1:42428df5a09dee3628dd88327d44b743aeb183f0 rather than PKG_FAIL_REASON, so that they provide useful error messages in build logs, and so that they continue to work on platforms where they aren't broken. 2005-12-26T23:39:30Z schmonz schmonz@pkgsrc.org 2005-12-26T23:39:30Z urn:sha1:463f43526a7b74edae99d0ed1a9ef0ad86a43c45 3.0. If one of these is important to you, please fix it in time for pkgsrc-2006Q1, or it may be removed.