6:15 a.m.
Hi,
a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are some
changes which affect everyone who builds with xulrunner-devel-unstable
package.
Mozilla decided to merge all include directories to one (mozbz#398573)
and stop shipping stable/unstable packages. So all headers/libraries are
merged to one big xulrunner-devel package (with respective pkgconfig
files) and xulrunner-devel-unstable has been removed.
What does it mean for you?
1) Change xulrunner-devel-unstable to xulrunner-devel in spec. file
BuildRequires.
2) Switch libxul-embedding-unstable.pc to libxul-embedding.pc or
libxul-unstable.pc to libxul.pc in make/configure scripts.
3) Rebuild the package and report any problem to BZ.
ma.
4:58 a.m.
On 11/19/2009 02:32 AM, Kevin Kofler wrote:
Martin Stransky wrote:
> Mozilla decided to merge all include directories to one (mozbz#398573)
> and stop shipping stable/unstable packages.
Does this mean the API will finally be kept stable? Or is it now even harder
to figure out what needs rebuilding and what not?
No code changes, just removed subdirs from include...
10:57 a.m.
Hi
Would you please explain how do you come up with the
Source0: %{name}-%{version}%{?pretag}.source.tar.bz2
taraballs?
Even better, include it in a comment in the spec file or the fedora wiki
somewhere.
I am trying to track a regression but having a hard time connecting
these source tarballs to something in ftp.mozilla.org or hg.mozilla.org.
TIA
Yanko
On Wed, 2009-11-18 at 13:15 +0100, Martin Stransky wrote:
Hi,
a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are
some
changes which affect everyone who builds with xulrunner-devel-unstable
package.
Mozilla decided to merge all include directories to one (mozbz#398573)
and stop shipping stable/unstable packages. So all headers/libraries
are
merged to one big xulrunner-devel package (with respective pkgconfig
files) and xulrunner-devel-unstable has been removed.
What does it mean for you?
1) Change xulrunner-devel-unstable to xulrunner-devel in spec. file
BuildRequires.
2) Switch libxul-embedding-unstable.pc to libxul-embedding.pc or
libxul-unstable.pc to libxul.pc in make/configure scripts.
3) Rebuild the package and report any problem to BZ.
ma.
11:52 a.m.
On Thursday 19 November 2009 08:57:26 am Yanko Kaneti wrote:
Hi
Would you please explain how do you come up with the
Source0: %{name}-%{version}%{?pretag}.source.tar.bz2
taraballs?
Even better, include it in a comment in the spec file or the fedora wiki
somewhere.
I am trying to track a regression but having a hard time connecting
these source tarballs to something in ftp.mozilla.org or hg.mozilla.org.
For what it's worth, I filed this bug a long time ago:
https://bugzilla.redhat.com/show_bug.cgi?id=521704
Regards,
--
Conrad Meyer <cemeyer(a)u.washington.edu>
4:30 p.m.
On 11/18/2009 04:15 AM, Martin Stransky wrote:
a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are
some
changes which affect everyone who builds with xulrunner-devel-unstable
package.
Mozilla decided to merge all include directories to one (mozbz#398573)
and stop shipping stable/unstable packages. So all headers/libraries are
merged to one big xulrunner-devel package (with respective pkgconfig
files) and xulrunner-devel-unstable has been removed.
What does it mean for you?
1) Change xulrunner-devel-unstable to xulrunner-devel in spec. file
BuildRequires.
Perhaps we should continue to provide -unstable, though. Things that
still need the unstable libs can continue Require -unstable which will
make it a heck of a lot easier to figure out what to rebuild...
7:38 p.m.
On Thu, 2009-11-19 at 14:30 -0800, Christopher Aillon wrote:
On 11/18/2009 04:15 AM, Martin Stransky wrote:
> a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are some
> changes which affect everyone who builds with xulrunner-devel-unstable
> package.
>
> Mozilla decided to merge all include directories to one (mozbz#398573)
> and stop shipping stable/unstable packages. So all headers/libraries are
> merged to one big xulrunner-devel package (with respective pkgconfig
> files) and xulrunner-devel-unstable has been removed.
>
> What does it mean for you?
>
> 1) Change xulrunner-devel-unstable to xulrunner-devel in spec. file
> BuildRequires.
Perhaps we should continue to provide -unstable, though. Things that
still need the unstable libs can continue Require -unstable which will
make it a heck of a lot easier to figure out what to rebuild...
+1
Putting the unstable API in a separate package also makes it a bit
harder for developers using Fedora as their development platform to
naively rely on the unstable API.
--
Braden McDaniel <braden(a)endoframe.com>
7:17 a.m.
to, 2009-11-19 kello 14:30 -0800, Christopher Aillon kirjoitti:
Perhaps we should continue to provide -unstable, though. Things that
still need the unstable libs can continue Require -unstable which will
make it a heck of a lot easier to figure out what to rebuild...
+1. I'd like to see a decision made soon on whether you will provide
-unstable or not. My xulrunner unstable dependent package (mozvoikko)
has been broken in Rawhide for a few days now, I'd like to know which
will be the best way to fix it.
--
Ville-Pekka Vainio
5:34 a.m.
On 11/22/2009 02:17 PM, Ville-Pekka Vainio wrote:
to, 2009-11-19 kello 14:30 -0800, Christopher Aillon kirjoitti:
> Perhaps we should continue to provide -unstable, though. Things that
> still need the unstable libs can continue Require -unstable which will
> make it a heck of a lot easier to figure out what to rebuild...
+1. I'd like to see a decision made soon on whether you will provide
-unstable or not. My xulrunner unstable dependent package (mozvoikko)
has been broken in Rawhide for a few days now, I'd like to know which
will be the best way to fix it.
Okay, what about this:
- all packages should switch to unified mozilla package config files,
libxul-embedding.pc & libxul.pc. Old libxul-embedding-unstable.pc &
libxul-unstable.pc will be provided for compatibility.
- packages built against unfrozen interfaces will keep BuildRequire:
gecko-devel-unstable. It helps mozilla team to decide which packages
should be rebuild in update.
You may identify frozen (stable) interface by:
- at http://www.mozilla.org/projects/embedding/EmbedInterfaceFreeze.html
- at sources - look for "@status" string in appropriate idl file (in
/usr/share/idl/xulrunner-sdk-1.9.2), all frozen interfaces have status
"FROZEN" there.
Recently, a few F12 packages (looks like browser plug-ins only) are
built against frozen (stable) interface [1] and all others require
unstable interface.
ma.
[1]:
gecko-sharp2-0:0.13-13.fc12.src
gnome-chemistry-utils-0:0.10.8-1.fc12.src
gxine-0:0.5.903-4.fc12.src
libproxy-0:0.2.3-12.fc12.src
openoffice.org-1:3.1.1-19.14.fc12.src
openvrml-0:0.18.3-5.fc12.src
6:27 a.m.
On 11/23/2009 12:34 PM, Martin Stransky wrote:
On 11/22/2009 02:17 PM, Ville-Pekka Vainio wrote:
> to, 2009-11-19 kello 14:30 -0800, Christopher Aillon kirjoitti:
>> Perhaps we should continue to provide -unstable, though. Things that
>> still need the unstable libs can continue Require -unstable which will
>> make it a heck of a lot easier to figure out what to rebuild...
>
> +1. I'd like to see a decision made soon on whether you will provide
> -unstable or not. My xulrunner unstable dependent package (mozvoikko)
> has been broken in Rawhide for a few days now, I'd like to know which
> will be the best way to fix it.
>
Okay, what about this:
- all packages should switch to unified mozilla package config files,
libxul-embedding.pc & libxul.pc. Old libxul-embedding-unstable.pc &
libxul-unstable.pc will be provided for compatibility.
built as xulrunner-1.9.2.1-0.4.b3.fc13.
- packages built against unfrozen interfaces will keep BuildRequire:
gecko-devel-unstable. It helps mozilla team to decide which packages
should be rebuild in update.
You may identify frozen (stable) interface by:
- at http://www.mozilla.org/projects/embedding/EmbedInterfaceFreeze.html
- at sources - look for "@status" string in appropriate idl file (in
/usr/share/idl/xulrunner-sdk-1.9.2), all frozen interfaces have status
"FROZEN" there.
Recently, a few F12 packages (looks like browser plug-ins only) are
built against frozen (stable) interface [1] and all others require
unstable interface.
ma.
[1]:
gecko-sharp2-0:0.13-13.fc12.src
gnome-chemistry-utils-0:0.10.8-1.fc12.src
gxine-0:0.5.903-4.fc12.src
libproxy-0:0.2.3-12.fc12.src
openoffice.org-1:3.1.1-19.14.fc12.src
openvrml-0:0.18.3-5.fc12.src
2:21 a.m.
2009/11/18 Martin Stransky <stransky(a)redhat.com>:
Hi,
a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are some
changes which affect everyone who builds with xulrunner-devel-unstable
package.
Mozilla decided to merge all include directories to one (mozbz#398573) and
stop shipping stable/unstable packages. So all headers/libraries are merged
to one big xulrunner-devel package (with respective pkgconfig files) and
xulrunner-devel-unstable has been removed.
Is this the same with the -python and -python-devel pacakges?
Regards,
Peter
2:39 a.m.
On 11/20/2009 09:21 AM, Peter Robinson wrote:
2009/11/18 Martin Stransky<stransky(a)redhat.com>:
> Hi,
>
> a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are some
> changes which affect everyone who builds with xulrunner-devel-unstable
> package.
>
> Mozilla decided to merge all include directories to one (mozbz#398573) and
> stop shipping stable/unstable packages. So all headers/libraries are merged
> to one big xulrunner-devel package (with respective pkgconfig files) and
> xulrunner-devel-unstable has been removed.
Is this the same with the -python and -python-devel pacakges?
I'm not sure what's going on with python interface but it looks removed
from 3.6. I'm still investigating it...
7:05 p.m.
On Fri, Nov 20, 2009 at 8:39 AM, Martin Stransky <stransky(a)redhat.com> wrote:
On 11/20/2009 09:21 AM, Peter Robinson wrote:
>
> 2009/11/18 Martin Stransky<stransky(a)redhat.com>:
>>
>> Hi,
>>
>> a new firefox (3.6 beta 2) just hit rawhide (a.k.a f13). There are some
>> changes which affect everyone who builds with xulrunner-devel-unstable
>> package.
>>
>> Mozilla decided to merge all include directories to one (mozbz#398573)
>> and
>> stop shipping stable/unstable packages. So all headers/libraries are
>> merged
>> to one big xulrunner-devel package (with respective pkgconfig files) and
>> xulrunner-devel-unstable has been removed.
>
> Is this the same with the -python and -python-devel pacakges?
I'm not sure what's going on with python interface but it looks removed from
3.6. I'm still investigating it...
Having a quick google around the mozilla.org site I found the
following mercurial repo [1] so it looks like its been split out to a
separate project but I'm not 100% sure. Its used by
hulahop/sugar-browse so it would be useful to add back in some form or
another but I has issues building it but then I know very little about
the mozilla build system.
Cheers,
Peter
[1] http://hg.mozilla.org/pyxpcom
5267
days inactive
5283
days old
12 comments
8 participants
participants (8)
-
Braden McDaniel -
Christopher Aillon -
Conrad Meyer -
Kevin Kofler -
Martin Stransky -
Peter Robinson -
Ville-Pekka Vainio -
Yanko Kaneti