core/mlocate/updatedb.conf

#
# /etc/updatedb.conf
#
# configuration file for updatedb(8), see updatedb.conf(5)

PRUNEFS="nfs nfs4 afs proc smbfs cifs autofs auto iso9660 sshfs sysfs usbfs tmpfs"
PRUNENAMES=".git .svn .hg .bzr _darcs CVS RCS"
PRUNEPATHS="/tmp /mnt /var/cache /var/lock /var/run /var/spool /var/tmp"

# End of file
mlocate: initial release thought long about creating an empty /var/lib/mlocate/mlocate.db within the port or not. Decided to do not, because its boring if with every new update of the port, the database is rubbed out and the user has to run updatedb to get back a functional locate. 2008-10-31 10:37:40 +01:00			`#`
			`# /etc/updatedb.conf`
			`#`
mlocate: update to 0.22.3 2010-03-05 11:04:33 +01:00			`# configuration file for updatedb(8), see updatedb.conf(5)`
mlocate: initial release thought long about creating an empty /var/lib/mlocate/mlocate.db within the port or not. Decided to do not, because its boring if with every new update of the port, the database is rubbed out and the user has to run updatedb to get back a functional locate. 2008-10-31 10:37:40 +01:00
mlocate: update to 0.22.3 2010-03-05 11:04:33 +01:00			`PRUNEFS="nfs nfs4 afs proc smbfs cifs autofs auto iso9660 sshfs sysfs usbfs tmpfs"`
			`PRUNENAMES=".git .svn .hg .bzr _darcs CVS RCS"`
			`PRUNEPATHS="/tmp /mnt /var/cache /var/lock /var/run /var/spool /var/tmp"`
mlocate: initial release thought long about creating an empty /var/lib/mlocate/mlocate.db within the port or not. Decided to do not, because its boring if with every new update of the port, the database is rubbed out and the user has to run updatedb to get back a functional locate. 2008-10-31 10:37:40 +01:00
			`# End of file`