Hello,
I'm currently trying to package Cryptpad[^1].
It is a NodeJS application that provides a collaborative end-to-end 
encrypted office suite.
I have a difficult time to find the best approach for packaging it due 
to the following aspects:

1. Is it recommended to store NodeJS source files in /usr/share or 
/usr/bin? It also includes scripts for data management that need to stay 
in place relative to the source dir.

2. The data directory needs to be a subdirectory of the source directory 
(e.g. /usr/share/cryptpad/data). Symlinks are fine. What is the best 
approach for this? Currently I'm creating a symlink to /var/lib/cryptpad 
in the install phase of the APKBUILD.

3. The source directory includes a script that downloads multiple 
versions of OnlyOffice that slow down the build process considerably.

4. The source directory (including the required node_modules) is quite 
large (~1.3GiB). As the entire source directory is packaged, the 
resulting packages is quite large.

What is the best approach for packaging such a project that doesn't 
adhere to the "standard" application model?

Kind regards and thank you for your attention
Paul ~pfzetto


[^1]: https://cryptpad.fr

Op 27-07-2026 om 18:42 schreef pfzetto:

> Hello,
> I'm currently trying to package Cryptpad[^1].
> It is a NodeJS application that provides a collaborative end-to-end 
> encrypted office suite.
> I have a difficult time to find the best approach for packaging it due 
> to the following aspects:
>
> 1. Is it recommended to store NodeJS source files in /usr/share or 
> /usr/bin? It also includes scripts for data management that need to 
> stay in place relative to the source dir.
/usr/lib IMO
>
> 2. The data directory needs to be a subdirectory of the source 
> directory (e.g. /usr/share/cryptpad/data). Symlinks are fine. What is 
> the best approach for this? Currently I'm creating a symlink to 
> /var/lib/cryptpad in the install phase of the APKBUILD.
>
> 3. The source directory includes a script that downloads multiple 
> versions of OnlyOffice that slow down the build process considerably.
I don't think it should be in aports if it depends on Onlyoffice as it's 
a licensing trap through removing Freedom 0. 
https://www.onlyoffice.com/blog/2026/03/onlyoffice-flags-license-violations-in-euro-office-project-by-nextcloud-and-ionos#:~:text=Pursuant,e%29%29%2E 

>
> 4. The source directory (including the required node_modules) is quite 
> large (~1.3GiB). As the entire source directory is packaged, the 
> resulting packages is quite large.
>
> What is the best approach for packaging such a project that doesn't 
> adhere to the "standard" application model?
>
> Kind regards and thank you for your attention
> Paul ~pfzetto
>
>
> [^1]: https://cryptpad.fr

-- 
LN Liberda
it/she, het/zij, to [coś]/ona
https://liberda.nl/