Page 2 of 22
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 3:06 pm
by Stevo
It's just that the dummy packages require a lot of tedious editing of the control file without any typos...a big challenge for me! But I'll get started on that.
Edit: The addition of the thunderbird-l10-xpi dummy packages went pretty quick once I realized I could just copypaste the list of Icedove l10n dummy packages and convert that list with search and replace. Starting the mx17+2 builds now. I notice from watching the memory usage that at some points the build consumes over 8 GB of RAM, so you have to be careful if you want to do more than one at once.
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 3:44 pm
by fehlix
Stevo wrote: Tue Jun 05, 2018 3:06 pm
It's just that the dummy packages require a lot of tedious editing of the control file without any typos...a big challenge for me! But I'll get started on that.
Not sure I undestand. What about this one meta-file control for fr_FR.
Code: Select all
Package: thunderbird-l10n-xpi-de
Version: 2:52.8.0-1~mx17+1
Architecture: all
Maintainer: Stevo
Installed-Size: xx
Depends: thunderbird-l10n-fr, lightning-l10n-fr
Section: localization
Priority: optional
Description: metapackage for thunderbird and lightning localization
This metapackage depends on loccalization packages for Thunderbird and Lightning-Calendar
Wouldn't the corresponding meta-packages with the avove control file just do what we want.
The control files for the xpi-metapacks could just be generated in one go for LANGs we have, or not?
-fehlix
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 3:56 pm
by Stevo
fehlix wrote: Tue Jun 05, 2018 3:44 pm
Stevo wrote: Tue Jun 05, 2018 3:06 pm
It's just that the dummy packages require a lot of tedious editing of the control file without any typos...a big challenge for me! But I'll get started on that.
Not sure I undestand. What about this one meta-file control for fr_FR.
Code: Select all
Package: thunderbird-l10n-xpi-de
Version: 2:52.8.0-1~mx17+1
Architecture: all
Maintainer: Stevo
Installed-Size: xx
Depends: thunderbird-l10n-fr, lightning-l10n-fr
Section: localization
Priority: optional
Description: metapackage for thunderbird and lightning localization
This metapackage depends on loccalization packages for Thunderbird and Lightning-Calendar
Wouldn't the corresponding meta-packages with the avove control file just do what we want.
The control files for the xpi-metapacks could just be generated in one go for LANGs we have, or not?
-fehlix
See my edit above for my quick way to generate the list. So the actual entry end up as:
Code: Select all
Package: thunderbird-l10n-xpi-de
Architecture: all
Section: oldlibs
Depends:
thunderbird-l10n-de (>= ${binary:Version}),
${misc:Depends},
Homepage: https://wiki.mozilla.org/L10n:Teams:de
Description: German language package for Thunderbird - Transitional package
This is a dummy package for the transition of the MX to Debian versions.
The goal of Thunderbird is to produce a cross platform stand-alone mail
application using the XUL user interface language.
.
This package contains the localization of Thunderbird in German.
.
This is a transitional package. It can be safely removed.
Also, I think you're confusing the control file that ends up in the deb for the debian/control file that generates it. There are some critical differences...you can look at the original in the debian.tar.xz tarball in the mx test repo for tbird. Now with my edits, it's well over 5000 lines long...
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 4:00 pm
by dolphin_oracle
nice! and I like the use of "oldlibs" for the section. those are usuallyremovable some how by some of the apt utilities.
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 4:10 pm
by Stevo
dolphin_oracle wrote: Tue Jun 05, 2018 4:00 pm
nice! and I like the use of "oldlibs" for the section. those are usuallyremovable some how by some of the apt utilities.
If we find out what they are, that would be a nice feature to add to "MX Cleanup" or whatever it ends up named.
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 4:41 pm
by fehlix
Stevo wrote: Tue Jun 05, 2018 3:56 pm
.. Also, I think you're confusing the control file that ends up in the deb for the debian/control file that generates it.
Well, indeed I've only looked into resulting deb-controls.
My example was just to demonstrate the idea and addionally
I have included the dependancy of both thunderbird-l10n and lightning-l10n
Based on the above example build-control all the other could be generated.
I can use your's above and I generate all the remainig one's
including the lighning-l10n.
Or just send me one which you think I can use for generating all
in one go.
... just a thought
EDIT: let me look into debian source first...lets see how to "generate" those above ...
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 5:42 pm
by Stevo
The current way the Debian version does the control file is just to use a separate package entry for every real and dummy package. I think the MX version used a separate language list file and some code to generate the entries for the langpacks from that file...which came from kmathern. But it was pretty easy to copy/paste/search/replace to generate the full list for our dummy packages, anyway. FWIW, it now generates over 300 packages for the build--600 if you count MX 15.
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 5:55 pm
by dolphin_oracle
Ok so we should get the pm files for mx-packageinstaller-pkglist updated too.
I'm thinking that instead of separate entries for lightning and thunderbird that we put both language packs in the thunderbird language pm files.
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 5:58 pm
by Stevo
Sounds good. Builds with dummies are done, but I'll ask Tim to put them in testing until everything in main and PM is squared away. Then we can purge the MX packages and move the new ones to main.
Re: MX 17 Repository: The Thunderbird Thread
Posted: Tue Jun 05, 2018 6:09 pm
by dolphin_oracle
Stevo wrote: Tue Jun 05, 2018 5:58 pm
Sounds good. Builds with dummies are done, but I'll ask Tim to put them in testing until everything in main and PM is squared away. Then we can purge the MX packages and move the new ones to main.
sounds good, that will give us a chance to enable test and try out the pm files too.