Closed Bug 300136 Opened 20 years ago Closed 19 years ago

Full update archives may need to contain remove commands

Categories

(Firefox Build System :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.8beta4

People

(Reporter: darin.moz, Assigned: mscott)

References

Details

(Keywords: fixed1.8)

Attachments

(3 files, 1 obsolete file)

Full update archives may need to contain remove commands. When we remove or move some file in a distribution, we need to include a corresponding "remove" command in the full update archive. For partial updates, this is already done by virtue of the fact that the partial update is generated from the differences between two distributions. After discussing this problem with bsmedberg and chase, we settled on leveraging packages-static's supposed support for "-" prefixed lines that specify files that should not be part of the distribution. We'll need to add a way to specify a remove list to make_full_update.sh, but that should be pretty straightforward.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.8beta4
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.5? → blocking1.8b4?
Flags: blocking1.8b4? → blocking1.8b4+
Flags: blocking1.8b4-
Flags: blocking1.8b4+
Flags: blocking-aviary1.5+
Flags: blocking1.8b5?
Flags: blocking1.8b5-
Flags: blocking-aviary1.5+
We definitely do need this.
Assignee: darin → benjamin
Status: ASSIGNED → NEW
Flags: blocking1.8b5? → blocking1.8b5+
benjamin: thanks for offering to help with this patch :) how do you plan to implement it? as i described in comment #0, or are you thinking about something else?
As described, using the "-" listings in the manifest to generate a file "removed.files" which would be shipped with the zip builds. The MAR-creator would then take this file and generate remove commands from it. The MAR process can remove entire directory trees, can't it?
This packages a removed-files list, and also uses the same list to generate files which need to be removed by the installer. The MAR creation script will need to be taught to read this file and generate the proper remove instructions.
Attachment #196070 - Flags: review?(darin)
Comment on attachment 196070 [details] [diff] [review] Package a removed-files list, rev. 1 >Index: browser/installer/removed-files.in >+defaults/pref/bug307259.js ... >+defaults/pref/bug259708.js Perhaps this should be listed up near the other bug's pref file? This patch looks good to me except that I don't understand why we need to (or want to) include removed-files in the resulting distribution. It would seem to be a file that is only needed by our distribution packaging scripts. I would not bother copying it onto users' systems. Or, do you believe that it might be useful one day to have that info on users' systems? r=darin
Attachment #196070 - Flags: review?(darin) → review+
I would like to preserve the possibility to go straight from tarball->MAR without any extra metadata if possible.
(In reply to comment #6) > I would like to preserve the possibility to go straight from tarball->MAR > without any extra metadata if possible. Why does that matter? Why would you want removed-files to be in the tarball?
> Why does that matter? Why would you want removed-files to be in the tarball? Mainly because we repackage the l10n builds from the tarball, so we need to have all the information there to make the MAR. But also "why not"? Checked in on trunk. I'm not quite sure how to process this list into a set of remove instructions in make_full_update.sh (and make_incremental_update.sh), so Darin or Chase needs to do that bit.
Assignee: benjamin → darin
Attachment #196070 - Flags: approval1.8b5?
Attached patch tbird changes to match (obsolete) — Splinter Review
Scott, since I'm on vacation next week could you review and land this?
Attachment #196218 - Flags: review?(mscott)
argh, a little too much blind copy-paste
Attachment #196218 - Attachment is obsolete: true
Attachment #196222 - Flags: review?(mscott)
Attachment #196218 - Flags: review?(mscott)
OK. I'll hack on make_full_update.sh and make_incremental_update.sh. I'll probably just add a command line option to specify the path to the "removed-files" file.
Darin, that shouldn't be necessary, since removed-files is in the archive.
Fair enough. So, if I find a file by the name of removed-files in the given directory, then I'll treat that as a list of files to be removed.
I'm not sure how to handle these lines in removed-files: chrome/overlayinfo/ defaults/profile/US/ updater.cpp does not understand how to recursively delete a directory. I suspect that asking it to remove a directory will simply fail, and it would probably cause the update archive to not apply. I'm considering skipping any lines in removed-files that end with a slash. I could extend updater.cpp to support recursive delete, but in this case it doesn't seem worth it since these directories should not exist anyways by the time software update runs (since they should have been removed by the installer). One concern I have is with tarball and zip based over-installs. Thoughts?
Attachment #196070 - Flags: approval1.8b5? → approval1.8b5+
Depends on: 308864
This broke packaging of non-Firefox builds on the trunk, since MOZ_PKG_REMOVALS is currently only defined for Firefox. A fix is in bug 308864.
FYI: I've got partial patches to make_full_update.sh and make_incremental_update.sh in my tree. I'm hoping to find the time to finish the changes tomorrow.
This patch includes changes to append the remove commands to all MAR files.
Attachment #197051 - Flags: review?(chase)
Comment on attachment 197051 [details] [diff] [review] v1 patch: mar packaging scripts Looks good.
Attachment #197051 - Flags: review?(chase) → review+
Comment on attachment 197051 [details] [diff] [review] v1 patch: mar packaging scripts Requesting 1.8 branch approval.
Attachment #197051 - Flags: approval1.8b5?
Attachment 197051 [details] [diff] is now checked in on the trunk. It looks like the only remaining thing to be done here is to land the patch for tbird (once mscott approves), right?
Status: NEW → ASSIGNED
Whiteboard: [needs review mscott]
Attachment #197051 - Flags: approval1.8b5? → approval1.8b5+
Keywords: fixed1.8
I'll check in the thunderbird changes once 308864 finds its way onto the branch.
Attachment 196070 [details] [diff] - fixed1.8 This is not yet entirely fixed1.8 until the tbird changes land.
Keywords: fixed1.8
-> mscott for tbird changes
Assignee: darin → mscott
Status: ASSIGNED → NEW
Comment on attachment 196222 [details] [diff] [review] tbird changes to match benjamin, this looked good to me. Did you intend to remove mail.jst from the list of installer_files in windows\Makefile.in though? I can check this in on the branch if you need me too.
Attachment #196222 - Flags: review?(mscott) → review+
Yes, I removed "mail.jst" from the list because it is processed separately in the rule below.
Attachment #196222 - Flags: approval1.8b5+
fixed branch and trunk.
Status: NEW → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8
Resolution: --- → FIXED
Whiteboard: [needs review mscott]
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: