It seems that the current firefox88 spec file contains a lot of ccache-related material, but the official build flag is missing from the mozilla project config. I'm wondering if this was done on purpose (and if so, why it's done this way). If not, perhaps we should be using the officially documented way of building with ccache?
Actually I never fully got the pros and cons and the interaction of ccache native and OBS. I'm following your mailthread but currently I could add a "metoo" to the questions. The ccache support in the packages was contributed by @MSirringhaus
Well, my question on the mailing list never got answered.
From rereading the OBS instructions, it might be easier to keep the ccache configuration in the spec file than to use useccache:PACKAGE build flags on the OBS project, since those flags need to be specified separately for each package (i.e., they won't get automatically applied if a package gets duplicated under a new name). The alternative is to use Substitute: gcc-c++ gcc-c++ --enable-ccache, which automatically applies to all packages in a project, but I think this makes it hard to disable it for individual packages (in case it's somehow interfering with them).
In any case, we should probably use sccache instead of ccache, since the former supports Rust in addition to C and C++.
Why is home:manfred-h:devel:languages:rust:rust-1.76 in the repositories config? sequoia-octopus-librnp fails to build for Tumbleweed, because it needs newer rust.
Will there be a 15.7 repo to be compatible with SLE SP7? Even if there is no leap 15.7, the SP7 users of SLE (like us) would be thankful for compatible firefox-esr, Thunderbird etc. packages :)
Various versions of Python 3 are required to build the Mozilla packages, but I can't find any OBS projects that provide the necessary packages for 15.7. Do you know of any?
Hi,
there is a little confusion about the thunderbird packages in the different repos. E.g. factory is using esr (140.3.0) while others use the release channel (143.0), but all are named MozillaThunderbird.rpm
For firefox you have solved that very elegant by packaging MozillaFirefox and firefox-esr. Would that be possible for TB too, i.e. using MozillaThunderbird for the latest release and thunderbird-esr for the esr packages?
This prevents the packages in this project from building:
$ osc build --clean openSUSE_Tumbleweed x86_64 seamonkey.spec
Building seamonkey.spec for openSUSE_Tumbleweed/x86_64
Using local file: seamonkey.spec
Getting buildconfig from server and store to /home/psy/obs/mozilla/seamonkey/.osc/_buildconfig-openSUSE_Tumbleweed-x86_64
unknown keyword in config: require:
Getting buildinfo from server and store to /home/psy/obs/mozilla/seamonkey/.osc/_buildinfo-openSUSE_Tumbleweed-x86_64.xml
unknown keyword in config: require:
buildinfo is broken... it says:
unresolvable: preinstalls: nothing provides rpm
Comments 10
According to the OBS User Guide at https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.prjconfig.html#id-1.5.7.3.4.6.4.2.2.7 ccache support can be enabled per package by adding a build flag to the project config. For example:
BuildFlags: useccahe:firefox88
It seems that the current firefox88 spec file contains a lot of ccache-related material, but the official build flag is missing from the mozilla project config. I'm wondering if this was done on purpose (and if so, why it's done this way). If not, perhaps we should be using the officially documented way of building with ccache?
Actually I never fully got the pros and cons and the interaction of ccache native and OBS. I'm following your mailthread but currently I could add a "metoo" to the questions. The ccache support in the packages was contributed by @MSirringhaus
OK, let's see if anyone responds with advice.
Well, my question on the mailing list never got answered.
From rereading the OBS instructions, it might be easier to keep the ccache configuration in the spec file than to use
useccache:PACKAGEbuild flags on the OBS project, since those flags need to be specified separately for each package (i.e., they won't get automatically applied if a package gets duplicated under a new name). The alternative is to useSubstitute: gcc-c++ gcc-c++ --enable-ccache, which automatically applies to all packages in a project, but I think this makes it hard to disable it for individual packages (in case it's somehow interfering with them).In any case, we should probably use sccache instead of ccache, since the former supports Rust in addition to C and C++.
Why is home:manfred-h:devel:languages:rust:rust-1.76 in the repositories config? sequoia-octopus-librnp fails to build for Tumbleweed, because it needs newer rust.
Will there be a 15.7 repo to be compatible with SLE SP7? Even if there is no leap 15.7, the SP7 users of SLE (like us) would be thankful for compatible firefox-esr, Thunderbird etc. packages :)
Various versions of Python 3 are required to build the Mozilla packages, but I can't find any OBS projects that provide the necessary packages for 15.7. Do you know of any?
Sorry, that slipped through. No, I am not, but there is indeed no problem using the 15.6 packages in sp7!
Hi, there is a little confusion about the thunderbird packages in the different repos. E.g. factory is using esr (140.3.0) while others use the release channel (143.0), but all are named MozillaThunderbird.rpm For firefox you have solved that very elegant by packaging MozillaFirefox and firefox-esr. Would that be possible for TB too, i.e. using MozillaThunderbird for the latest release and thunderbird-esr for the esr packages?
According to the Repositories tab of this project, the paths for openSUSE_Leap_15.6 and openSUSE_Tumbleweed have been deleted:
This prevents the packages in this project from building:
@wrosenauer Any chance you could have a look?