• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Upgrading a package doesn't remove obsolete files from previous version
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Upgrading a package doesn't remove obsolete files from previous version


  • Subject: Re: Upgrading a package doesn't remove obsolete files from previous version
  • From: Stephane Sudre <email@hidden>
  • Date: Thu, 19 Jul 2012 15:36:34 +0200

On Thu, Jul 19, 2012 at 3:29 PM, Jaroslav Šnajdr <email@hidden> wrote:
> Hello everyone,
>
> I created a flat package using pkgbuild:
>
> pkgbuild --root ... --scripts ... --identifier ... --version ...
> --install-location / package.pkg
>
> and then created a distribution package using productbuild.
>
> I don't use any special configuration file for pkgbuild - just grab whatever
> there is in the 'root' directory and create a package from it.
>
> The problem is that on upgrade, obsolete files from the old version are not
> deleted. Previous version, for example, installed the file:
>
> /usr/local/myproduct/lib/hibernate-4.1.0.jar
>
> and the new needs to replace the file with a new version -
> hibernate-4.1.1.jar. The old file must be removed. But it isn't. Both files
> are there side by side after the upgrade.
>
> It's probably important to mention that my installer is a server product -
> it's not an application bundle. It is installed to the disk root, into
> /usr/local. The pkg-info file can contain special instruction about
> upgrading bundles (BundleOverwriteAction etc), but what about files that are
> outside a bundle? There is a recent thread (from June) about a similar
> problem, but it was bundle-specific and discussed BundleOverwriteAction.

The first 2 things to check would be:

#1. Did you install the previous version using an installation
package? Because if you didn't, then the installation process has no
way to figure out some files have been removed.

#2. If you installed the previous version using an installation, are
the 2 packages sharing the same identifier? Because if they don't, the
installation process has no way to figure out that it's the same
"installer" and to remove files that are no more in the newer payload.




--
Packaging Resources - http://s.sudre.free.fr/Packaging.html

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Upgrading a package doesn't remove obsolete files from previous version
      • From: Jaroslav Šnajdr <email@hidden>
References: 
 >Upgrading a package doesn't remove obsolete files from previous version (From: Jaroslav Šnajdr <email@hidden>)

  • Prev by Date: Upgrading a package doesn't remove obsolete files from previous version
  • Next by Date: Re: Trying to include serial key with Adobe Lightroom package
  • Previous by thread: Upgrading a package doesn't remove obsolete files from previous version
  • Next by thread: Re: Upgrading a package doesn't remove obsolete files from previous version
  • Index(es):
    • Date
    • Thread