Packages Required

[paddatrapper]

The following javascript projects need packaging (separately from LT):

• blockui
• bootstrap-datetime (the package in Debian is not the same, can we migrate?)
• colorpicker
• contextmenu - This has changes made to it that need upstreaming or the project needs to be forked under a new name
• fullcalendar - This has changes made to it that need upstreaming or the project needs to be forked under a new name
• i18n
• js-timezone-detect
• dropzone
• moment-timezone
• stickypanel (No longer required)
• serverbrowse - This has changes made to it that need upstreaming or the project needs to be forked under a new name
• setup (it is homegrown, and so doesn't need separate packaging)
• sprintf
• tipsy - This has changes made to it that need upstreaming or the project needs to be forked under a new name (The pure upstream is available in Debian)
• waveformplaylist (it is homegrown, and so doesn't need separate packaging)
• [showinfo] (No longer needed)

The following PHP projects need packaging:

• [php-soundcloud] (No longer needed)

The following Python projects need packaging:

• wsgiref

The following HTML5/Flash projects need packaging:

• muses

[hairmare]

Are you sure that you don't want to / can't bundle javascript libraries into the libretime install?

If all libs need separate packages I'm pretty sure that there are heaps more in the libretime-<version>.tar.gz tarball that need their own packages (ie. some python stuff certainly).

In the PHP case, If you do not plan on using the bundled vendor/ directory you can probably use githubs <version>.tar.gz tarball instead.

I've noticed that some of the patched js libraries already address our concerns, so refactoring to more recent upstreams can help there as well (I've went down a large js refactor rabbit-hole while I was releasing alpha 2 but haven't come to an end yet).

[paddatrapper]

Are you sure that you don't want to / can't bundle javascript libraries into the libretime install?

Debian policy prevents this. External libraries cannot be bundled in the package, rather packaged separately.

If all libs need separate packages I'm pretty sure that there are heaps more in the |libretime-<version>.tar.gz| tarball that need their own packages (ie. some python stuff certainly).

I do not know the code base well enough to spot these, so if there are can you please point them out?

In the PHP case, If you do not plan on using the bundled vendor/ directory you can probably use githubs |<version>.tar.gz| tarball instead.

The Debian package needs to depend on the PHP library's package. So tarballs are useful only in doing the actual packaging, but still needs to be separate.

I've noticed that some of the patched js libraries already address our concerns, so refactoring to more recent upstreams can help there as well (I've went down a large js refactor rabbit-hole while I was releasing alpha 2 but haven't come to an end yet).

+1

[hairmare]

If all libs need separate packages I'm pretty sure that there are heaps more in the |libretime-.tar.gz| tarball that need their own packages (ie. some python stuff certainly).

I do not know the code base well enough to spot these, so if there are can you please point them out?

I think pydispatcher and python-vine might be missing from debian, also mutagen might need changes since pypo currently uses a specific version in setup.py.

[paddatrapper]

Thanks. I shall check those out

[Lapotor]

Can you provide the links to the JS Projects from the start post?

[Lapotor]

I searched the open things from top
Bootstrap-Datetime:

• https://packages.debian.org/sid/libjs-eonasdan-bootstrap-datetimepicker

Colorpicker:

• https://packages.debian.org/sid/libjs-jquery-colorpicker

Dropzone:

• https://packages.debian.org/sid/libjs-dropzone (Not in package list of stretch or jessie)

sPrintf:

• https://packages.debian.org/sid/node-sprintf-js

Tipsy:

• https://packages.debian.org/sid/libjs-jquery-tipsy

I hope that may help

[paddatrapper]

Thanks. I shall find more links when I get a chance tomorrow. In the mean time, those can be ticked off the list

[paddatrapper]

@hairmare should I create LT issues for the modified library issues?

[hairmare]

Some of the lib changes probably need taking care of by updating and fixing the code to use packages. We might not be able to upstream changes due to us not having originally done them (depending on the project) so we would need to re-implement those.

LibreTime issues might help but I'm a bit afraid that doing the long overdue big refactor of the frontend code will be the only way to get rid of some of the deeply embedded libs that where embedded and locally modified.

[paddatrapper]

@Lapotor, I've added links to the outstanding packages. I am busy packaging js-timezonedetect here, the only things missing are the IPT and the upload, which I shall do tonight. moment-timezone is also ready for IPT and upload