Radish alpha
H
rad:z3QDZAW2FAfuLvihrhiyDC9fAD8G9
HardenedBSD Package Manager
Radicle
Git
Add question from Peter Jeremy and reply from Matthew Seaman <matthew@FreeBSD.org> to FAQ
Baptiste Daroussin committed 13 years ago
commit 02f8a139532c32b63d21e36ebc67d3ca76a92813
parent 6ac9dc0
1 file changed +80 -0
modified FAQ.md
@@ -22,6 +22,15 @@ Table of Contents
* [How can I use pkgng with portmaster?](#15)
* [How can I use pkgng with portupgrade?](#16)
* [pkgng does not work it says: /usr/local/sbin/pkg: Undefined symbol "pkg_event_register"](#17)
+
* [Can pkgng cope with parallel installs?  What happpens if I simultaneously (attempt to) install conflicting packages?](#18)
+
* [If I use "pkg delete -f", what happens to packages that depended on the forcibly-deleted package?](#19)
+
* [What happens if I delete a package where I've modified one of the files managed by the package?](#20)
+
* [What facilities does it have for auditing and repairing the package database? (ie checking for inconsistencies between installed files and the content of the package database)?](#21)
+
* [Will it detect that a package install would overwrite an existing?](#22)
+
* [If so, what happens to the file metadata (particularly uid, gid and mtime)?](#23)
+
* [Can it track user-edited configuration files that are associated with packages?](#24)
+
* [Can it do 2- or 3-way merges of package configuration files?](#25)
+
* [The README states "Directory leftovers are automatically removed if they are not in the MTREE."  How does this work for directories that are shared between multiple packages?  Does this mean that if I add a file to a directory that was created by a package, that file will be deleted automatically if I delete the package?](#26)

<a name="0"></a>
### Q: How can I start using pkgng?
@@ -158,3 +167,74 @@ You should have forgotten make delete-old-libs when you upgraded your system.
during 9-CURRENT life the pkg_install tools has been splitted to provide a
shared library: libpkg.so.0 and this has been reverted, this error message means
that this library is still on your system, please check /usr/lib/libpkg.so.0
+

+
<a name="18"></a>
+
### Q: Can pkgng cope with parallel installs?  What happpens if I simultaneously (attempt to) install conflicting packages?
+

+
No.  Parallel installs will not work -- the first to start will lock the DB, and
+
the second won't be able to proceed.
+

+
<a name="19"></a>
+
### Q: If I use "pkg delete -f", what happens to packages that depended on the forcibly-deleted package?
+

+
Nothing.  If you forcibly delete a package it's assumed you understand that you know you're doing something that can break your system.
+
pkg check will detect missing dependency packages and reinstall as required.
+

+
<a name="20"></a>
+
### Q: What happens if I delete a package where I've modified one of the files managed by the package?
+

+
The package is removed, but modified file is not:
+

+
	# pkg check -s pciids
+
	pciids-20120625: checksum mismatch for /usr/local/share/pciids/pci.ids
+
	# pkg delete pciids
+
	The following packages will be deinstalled:
+
	
+
		pciids-20120625
+
	
+
	The deinstallation will free 788 kB
+
	Deinstalling pciids-20120625...pkg: /usr/local/share/pciids/pci.ids
+
	fails original SHA256 checksum, not removing
+
	pkg: rmdir(/usr/local/share/pciids/): Directory not empty
+
	done
+
	# pkg info pciids
+
	pkg: No package(s) matching pciids
+
	# ls -l /usr/local/share/pciids/pci.ids
+
	-rw-r--r--  1 root  wheel  752925 Jul 16 07:05
+
	/usr/local/share/pciids/pci.ids
+

+
<a name="21"></a>
+
### Q: What facilities does it have for auditing and repairing the package database? (ie checking for inconsistencies between installed files and the content of the package database)
+

+
See pkg-check(8)
+

+
<a name="22"></a>
+
### Q: Will it detect that a package install would overwrite an existing
+

+
Yes exactly that.  Files in the older package that are identical in the
+
newer one are left untouched.  Otherwise, files from the older package
+
are removed, and files from the newer package are installed.
+

+
<a name="23"></a>
+
### Q: If so, what happens to the file metadata (particularly uid, gid and mtime)?
+

+
Nothing.
+

+
<a name="24"></a>
+
### Q: Can it track user-edited configuration files that are associated with packages?
+

+
This works in exactly the same way as it does currently in the ports. Except if the package provide the configuration with a .pkgconf extension
+
In that if there is no user config the default configuration is created otherwise, the user edited version is kept
+

+
<a name="25"></a>
+
### Q: Can it do 2- or 3-way merges of package configuration files?
+

+
No.  In general the package will install sample configuration files,
+
and will only touch the live config files if either the live configs
+
don't exist, or the live configs are identical to the sample configs.
+
This is the standard way things work in the ports at the moment.
+

+
<a name="26"></a>
+
### Q: The README states "Directory leftovers are automatically removed if they are not in the MTREE."  How does this work for directories that are shared between multiple packages?  Does this mean that if I add a file to a directory that was created by a package, that file will be deleted automatically if I delete the package?
+

+
No.  Directories have to be empty before they will be removed.