How to handle JPG/PNG Assets in Recipe?

[sage-etcher]

Is there a way to handle asset files in Recipes? I see the NCSA-Mosaic package has a .png asset in the recipe's root level directory, is this the recommended approach?

Recipes/NCSA-Mosaic/git/mosaic64.png

[nuc1eon]

I'm surprised as well that there's not a more elegant way. At least have I never seen it being practiced differently.
See for instance:

• https://github.com/gobolinux/Recipes/tree/master/VCG/1.30 (core, gmon.out)
• https://github.com/gobolinux/Recipes/tree/master/Thunderbird/11.0 (thunderbird.desktop)
• https://github.com/gobolinux/Recipes/tree/master/Firefox/51.0 (firefox.desktop)

These recipes hold their "assets" in recipe's root level directory as well.

@hishamhm Has it never been considered to handle "assets" more elegantly? Is keeping them in the root directory a design choice, or was it just practiced straight out of 'convenience'?

I could imagine a subdirectory like Resources/Data or Resources/Assets to make sense. However granted, the cases asset files are needed are quite rare in practice.

I'd be curious to hear your thoughts^^

[hishamhm]

IIRC Resources gets copied wholesale into the Resources folder of the Programs entry, doesn't it? Not sure. If so, putting assets in Resources could end up copying twice. As for putting assets in the root of the recipe dir, I think we just found that ok at the time. I guess because assets don't have a predefined structure themselves and end up installed in custom places by the recipe. Defining a new Assets dir inside the recipe dir sounds equally fine to me.

…

On Wed, Apr 16, 2025, 21:36 Nuc1eoN ***@***.***> wrote: I'm surprised as well that there's not a more elegant way. At least have I never seen it being practiced differently. See for instance: - https://github.com/gobolinux/Recipes/tree/master/VCG/1.30 (core, gmon.out) - https://github.com/gobolinux/Recipes/tree/master/Thunderbird/11.0 ( thunderbird.desktop) - https://github.com/gobolinux/Recipes/tree/master/Firefox/51.0 ( firefox.desktop) These recipes hold their "assets" in recipe's root level directory as well. @hishamhm <https://github.com/hishamhm> Has it never been considered to handle "assets" more elegantly? Is keeping them in the root directory a design choice, or was it just practiced out of 'convenience'? I could imagine a subdirectory like Resources/Data or Resources/Assets to make sense. However granted, the cases asset files are needed are quite rare in practice. I'd be curious to hear your thoughts^^ — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB365IOPHMERWUB7PR7ABL2Z3ZQ7AVCNFSM6AAAAAB3I7OGF2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBWGA4DIMA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nuc1eon]

I am not sure right now whether Resources gets copied wholesale - I'll have to check.

Unless I am mistaken, Archlinux has no strict guideline on this as well. I've seen them being put in the root dir but also into a separate /assets folder in the root dir, if they spanned a bunch of files.

So maybe we could recommend to put them into an /Assets directory in the root folder, if they consist of a loose bunch of random files.

Thanks for your input!

[nuc1eon]

So maybe we could recommend to put them into an /Assets directory in the root folder, if they consist of a loose bunch of random files.

@sage-etcher What are your thoughts on this? I think that would be the simplest solution, no changes needed apart from updating our docs.

[sage-etcher]

Sounds excellent! 👍

[nuc1eon]

For reference, going forward we have decided to place these type of files in a directory called <recipe_root>/Data/ (rather than <recipe_root>/Assets/).

We've opted for Data/, because it seemed to fall more in line with the current naming conventions present within the GoboLinux ecosystem.