[Pkg-mozext-maintainers] BoF or Sprint while DebCamp or DebConf?

[Dmitry Smirnov]

On Thursday, 2 August 2018 1:13:00 PM AEST Ximin Luo wrote:
> I did some more tests and I think we can rely on touch-during-the-build for
> now, and avoid touch-during-postinst.
> [...] 
> This sequence of events suggests that firefox is caching the timestamp of
> manifest.json and comparing it with the previously-stored value, and *not*
> "the time it previously checked the files". So downgrading also works with
> an older timestamp.

Downgrading was one of my concerns but there are more (see my other email) 
such as package reinstall and quick maintainer's re-build of the package 
without touching changelog.


> I agree it's a bit more annoying for maintainers to deal with edits like
> this, but we can hopefully document this more clearly somewhere. Avoiding
> postinst I think is a worthy enough goal to put up with this.

I think it is better to touch manifest from postinst because it guarantees to 
reload extension every time.

If extension have symlinks to other packages then even "dpkg-reconfigure" 
would not be enough to pick up changes in other packages without touching 
manifest from postinst. IMHO your approach would not be reliable for more 
complex extensions with external dependencies.

Where did you push your changes? webext-devscripts repository is not updated 
yet:

  https://salsa.debian.org/webext-team/webext-devscripts

-- 
All the best,
 Dmitry Smirnov.

---

Lies are the social equivalent of toxic waste: Everyone is potentially
harmed by their spread.
        -- Sam Harris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-mozext-maintainers/attachments/20180802/6be80929/attachment.sig>