Bug#815006: Renaming Iceweasel to Firefox
Mike Hommey
mh at glandium.org
Tue Mar 1 23:18:56 UTC 2016
Time flies, and no upload has been done yet. I apologize for this. I've
been successively busy, then down with influenza.
Anyways, after having given this more thought, here are a few
observations on the implementation side:
- Since Debian hasn't had firefox* package in years, and even back then,
according to snapshot.debian.org, there weren't any firefox-l10n
packages (only individual firefox-locale-* packages), we can drop the
epoch in the l10n packages version numbers (woohoo! They were added
for no apparent reason ; at least none explained in the iceweasel-l10n
source package changelog).
- For the same reason, parts of the "upgrade" code can go away (things
that remove compreg.dat, xpti.dat and .autoreg, for instance ; or old
conffiles)
- Going around the debian/ directory, I realize libxul.pc as installed
in iceweasel-dev has been wrong since version 40... yet that went
largely unnoticed. Which brings the question: do we need to provide
pkgconfig files? They were justified back when xulrunner-dev existed,
but things have changed since then. And it's not like those files
exist upstream (they were part of xulrunner in some way, and never
existed when building Firefox ; the Firefox SDK has never come with
pkgconfig files). I'm tempted to say: "clean slate, start without them",
although the versioned paths in the -dev package are kind of
annoying...
- The information about sound in README.Debian is irrelevant to a new
package and some of the information in that file is actually outdated.
I doubt the instructions for java still work, for instance.
- Relatedly, the information in NEWS should probably move to README.Debian.
- Not related to switching to Firefox, but just adding this as a note to
myself, so as not to forget: I removed the menu file in iceweasel
44.0.2-1, but didn't remove the .xpm icon it was using. There is no
reason to keep that icon around.
- My plan is to upload an "independent" Firefox package (as in, with no
transitional package) that will follow Firefox releases every 6~8
weeks. Considering the timing in the current cycle, I might as well
wait for the release of Firefox 45 next week, although since the
package would have to go through NEW, it is also sensible to upload 44
ASAP to get a chance to get it out of NEW before 45 is released.
This package would have a permanent RC bug to prevent it from entering
testing, because it is not expected to be part of a Debian release.
- A separate "firefox-esr" source package would provide iceweasel and
iceweasel-l10n-* transitional package and would follow Firefox ESR
releases. Something that needs to be checked is what the Debian policy-
compliant way of moving the conffiles from /etc/iceweasel to
/etc/firefox-esr would be.
- Speaking of conffiles, version 46 is removing /etc/$package/profile.
I'm very tempted to remove it in 45 because that would only leave
/etc/iceweasel/pref/*.js to migrate, and would keep upgrade code free of
conffiles removal entirely. This would allow to simply use
/etc/firefox{,-esr}/*.js files.
Mike
More information about the pkg-mozilla-maintainers
mailing list