Comment 21 for bug 227945

Hello Lionel,

On Tue, Dec 9, 2008 at 9:32 AM, Lionel Le Folgoc wrote:
> On Tue, Dec 09, 2008 at 07:11:45AM -0000, John Vivirito wrote:
>> On 12/08/2008 09:21 AM, Lionel Le Folgoc wrote:
>> > Le lundi 08 décembre 2008 à 01:56:01, John Vivirito a écrit :
>> >> Added Ubuntu task and assigned asac to review and push as needed
>> >>
>> >
>> > There is already iceweasel-firegpg in unstable/main and jaunty/universe.
>> > Isn't it a better idea to merge it instead of repackaging it from
>> > scratch?
>> >
>> We dont use iceweasel we use abrowser. We shouldnt have to fix each of
>
> Where did I say that we use iceweasel?
>
>> the iceweasel packages to support other browsers since at this time it
>> only depends on iceweasel and the packages are not updated but ours
>> are.
>
> Right, I understand (this looks like duplicate work though). Then you may
> want to drop from the archive several iceweasel-* packages that landed in
> jaunty.
>
>> We dont merge any mozilla apps from debian and we havee it so they get
>> our packages.
>
> "it" == firegpg?
> "they" == debian?
> Why would Debian get our firegpg package?

I see your point, but we (Mozilla team) are currently using scripts
provided by mozilla-devscripts package for extensions packaging, in
particular xpi.mk and med-xpi-pack, to make the process easier to the
packager. The package is not available in Debian, and we are working
on the solution to include some part of that package in Debian too.
Until that happens, our and Debian's way of extension packaging
heavily differs, so it is not possible to reuse their packaging.

Also, asac and Volans are working on set of scripts which would
automatically check for newer versions of all our extensions and try
to auto-update packages. That is why we are maintaining packaging in
bzr branches. I'm not sure whether that will be included in Debian.

We are doing all of this in order to try to bring more extensions into
the archive, and to be able to give regularly updated extensions to
the user.

So, for now, some of the extensions are merged, those on which we
haven't worked on. In case firegpg has relatively newer version in
Debian, we could use that package, but I think it will be adapted at
some point to make use of scripts in mozilla-devscripts and
auto-update scripts.

I agree that diverge from Debian's packaging and double work are not
good in case they're not needed, but I think it's not the case here. I
hope that we will be able to include some of our work in Debian,
making the merging process a lot easier, at least with Debian using
mozilla-devscripts for extensions.

--
Best regards,
Saša Bodiroža