Void-packages: package request : Aseprite

[siduck765]

Aseprite is a tool to create animated sprites and pixel art

[kartikynwa]

https://github.com/aseprite/aseprite/

I don't understand the license for this. Are we permitted to distribute this from Void's package manager?

[flexibeast]

@kartikynwa: Looking at the FAQ, i would guess no.

[kartikynwa]

A restricted package should work, right?

[ghost]

There is also LibreSprite which was forked from Asprite when it was still gpl2 licenced.

If the void maintainers don't wan't to package Asprite this would be the next best alternative.

[siduck765]

https://github.com/aseprite/aseprite/

I don't understand the license for this. Are we permitted to distribute this from Void's package manager?

its available on aur and many repos tho , its paid but completely OSS

[ericonr]

If it's on the AUR it's still being built locally, so it isn't breaking licensing terms.

[rc-05]

There is also LibreSprite which was forked from Asprite when it was still gpl2 licenced.

If the void Maintainers don't wan't to package Asprite this would be the next best alternative.

I think that it's better to package the libre fork of Aseprite directly (thus completely ditching the proprietary version).

[ghost]

I think that it's better to package the libre fork of Aseprite directly (thus completely ditching the proprietary version).

It's OSS but not Free Software (in the FSF sense) IIRC.

Reading the EULA it seems that the only way to distribute Asprite on void is to provide a template that the user of the application needs to self compile using xbps-src (similar to discord). Like ericonr already said, if it's built locally it does not break the EULA.

(g) Source code.
You may only compile and modify the source code of the SOFTWARE PRODUCT for your own personal purpose or to propose a contribution to the SOFTWARE PRODUCT.

[rc-05]

I think that it's better to package the libre fork of Aseprite directly (thus completely ditching the proprietary version).

It's OSS but not Free Software (in the FSF sense) IIRC.

Reading the EULA it seems that the only way to distribute Asprite on void is to provide a template that the user of the application needs to self compile using xbps-src (similar to discord).

(g) Source code.
You may only compile and modify the source code of the SOFTWARE PRODUCT for your own personal purpose or to propose a contribution to the SOFTWARE PRODUCT.

So the restricted package can be created in a way that downloads a tarball of the source code of a specific version, but honestly I would just package the libre alternative as to completely avoid licensing issues and what not.