[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2 2006-04-07T15:28:49Z 2006-04-07T15:28:49Z jlam jlam 2006-04-07T15:28:49Z urn:sha1:62ac3cd6f1dd96a22ae496c710f567108f738230 2005-05-03T15:40:57Z wiz wiz 2005-05-03T15:40:57Z urn:sha1:6259b79f786db5c47b66b3a2773897699676c830 2005-05-02T20:33:57Z reed reed 2005-05-02T20:33:57Z urn:sha1:22c4e451098bcb1ffee496c70c2b37805278db1a And always is defined as share/examples/rc.d which was the default before. This rc.d scripts are not automatically added to PLISTs now also. So add to each corresponding PLIST as required. This was discussed on tech-pkg in late January and late April. Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere and remove the RCD_SCRIPTS_EXAMPLEDIR itself. 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-04-23T22:07:52Z reed reed 2004-04-23T22:07:52Z urn:sha1:cba182b47fc5b42f77862f4b5a18898200c81105 the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too. 2004-03-10T00:56:54Z seb seb 2004-03-10T00:56:54Z urn:sha1:bd68b9789590169e2485e20c49b090449f904c3e 2003-08-05T11:17:10Z seb seb 2003-08-05T11:17:10Z urn:sha1:1a7bbbc314e152183acf9ed82e73fa769ab6d8f6 2003-03-23T14:28:31Z lukem lukem 2003-03-23T14:28:31Z urn:sha1:c761f5c34484512ddf80a7f5f6a855254ba92dba use /var/sfs instead of /usr/pkg/var/sfs use OWN_DIRS_PERMS bump PKGREVISION 2003-03-22T22:07:22Z lukem lukem 2003-03-22T22:07:22Z urn:sha1:b1acf50bdcf37e49f28fd1ead587f5abf5d1614d reference to them in the distribution, either): bin/fake-agent bin/rpc_pcl bin/rpc_psrv bin/smkdirall bin/smount bin/snfsfstab bin/snfshost bin/snfsmount bin/snfspsrv bin/snfsumount bin/snfsuser bin/sumount bin/sumountall etc/rpc_pcl.conf lib/perl5/site_perl/5.6.1/SNFS.pm lib/perl5/site_perl/5.6.1/auto/SNFS/autosplit.ix 2003-03-17T21:01:47Z agc agc 2003-03-17T21:01:47Z urn:sha1:f44693816576fd13115b305f3336532614b14e50 Based on the sfs-0.6 package provided by Michael Santos in PR 18528. SFS is a secure, global network file system with completely decentralized control. SFS lets you access your files from anywhere and share them with anyone, anywhere. Anyone can set up an SFS server, and any user can access any server from any client. SFS lets you share files across administrative realms without involving administrators or certification authorities.