Creating separate debug package

Alec Leamas leamas.alec at gmail.com
Wed Sep 25 05:39:34 UTC 2019


Hi Ryan,

Thanks for taking time to reply!

> On 25/09/2019 05:52, Ryan Gonzalez wrote:
> This should happen automatically unless no-debuginfo is in your
> manifest. I think the debug info is installed by default when you
> install via flatpak-builder, which could be why you're seeing the large
> app size.
> 
> On Tue, Sep 24, 2019, 3:36 PM Alec Leamas <leamas.alec at gmail.com
> <mailto:leamas.alec at gmail.com>> wrote:
> 
>     Dear list,
> 
>     So, I have a package which is just too big, and the reason is basically
>     the contents of /app/lib/debug. I suppose the problem to split my
>     package into a base package + a debug (extension?) is solved since long,
>     but I'm too dumb to find the solution.
> 
>     Any wisdom in this list?

>  On 25/09/2019 05:52, Ryan Gonzalez wrote:
>> This should happen automatically unless no-debuginfo is in your
>> manifest. I think the debug info is installed by default when you
>> install via flatpak-builder, which could be why you're seeing the large
>> app size.

Perhaps.. But I just don't get it. My workflow is basically

    flatpak-builder  --force-clean app org.opencpn.OpenCPN.yaml
    flatpak build-export repo/repo app stable
    flatpak install -y --user --reinstall \
            repo/repo org.opencpn.OpenCPN

---> At this point I suppose anything might happen, so:
    flatpak --user uninstall org.opencpn.OpenCPN

---> and then, trying to verify the overall workflow:
    flatpak build-sign  [...] repo/repo
    flatpak build-update [...] repo/repo
    # sign *flatpakref and *flatpakrepo
    rcp repo *flatpakref *flatpakrepo ssh:remote-ssh-location
    flatpak --user install  http://remote-http_location/repo

The package I get this way is about 200Mb, most of which /app/lib/debug
stuff. I suppose I do some things wrong, but which?

Cheers!
--alec






More information about the Flatpak mailing list