Hello, > The UNO package manager does keep unaltered copies of the (packed) UNO > packages, which clearly belong to the wrapping native packages and can > be checksummed. The 'cache' area where the contents of the UNO package > files are unpacked and merged files are created is owned exclusively by > the UNO package manager. But it is true that a native package manager > can't know which of these files depend on what UNO package and in what > way, so checking or restoring the integrity of this data must be done by > invoking the UNO package manager.
The packagemanager stores the package _inflated_ (only) in its cache. Eg, it is possible to install a package coming with some Basic scripts, modifying these using the OOo Basic IDE, then exporting the _modified_ package. This differs from the former pkgchk approach which has kept a truly unmodified deflated copy in uno_packages while operating on inflated data in its cache. [For backward compatibility, unmodified deflated copies are stored _only_ for packages coming via pkgchk; pkgchk will most probably vanish after OOo 2.0.] > Not sure what you mean by 'provide sources'? (Copies of) all installed > packages are kept unaltered in the 'canonical place', so yes, you can > remove the cache directory contents and regenerate it. If you delete the cache, your unopkg/PackageManager UI added packages are lost. The only supported way to _regenerate_ the caches is unopkg reinstall [--shared] Don't delete/patch any directories or the like, the caching structure is private and a moving target, for good reason. regards, --Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
