thanks - help is always appreciated it is not a simple problem - i suspect that neither a symlink nor hard-link would work - the problem is that if 'firefox' is installed during migration from another arch to parabola, 'iceweasel' will replace 'firefox'; but the arch firefox extensions would remain installed under /usr/lib/firefox/
it is not yet clear if the plan is feasible, nor if the full combination of conflicts/replaces/provides, behaves as i suppose this plan is ripe for exposing and creating bugs - eg: if any add-on running under iceweasel stores config to ~/.mozilla/firefox, that add-on may be borked the build already migrates ~/.mozilla/firefox to ~/.mozilla/iceweasel; but it was intended to be temporary - it may need to be adopted permanently to leave that symlink behind after migration over-all, it may be tricky to allow other (user-installed) firefox variants to co-exist, without shared/conflicting configuration, some trivial but fatal mis-configurations, like a confused $MOZ_APP_NAME env var, etc however if it works, the larger benefit would be that all, or most currently packaged (and blacklisted) arch packages, could be dropped from the blacklist at once, and all would "just work" _______________________________________________ Dev mailing list [email protected] https://lists.parabola.nu/mailman/listinfo/dev
