Ticket #965 (closed task: wontfix)

Opened 3 years ago

Last modified 22 months ago

Update add-on packaging

Reported by: matija Owned by: matija
Milestone: Future Component: web
Severity: minor Keywords:
Cc: mitar Blocking:
Blocked By:

Description

Add-on packaging has fallen behind during our infrastructure upgrade, so add-ons are no longer properly packaged. Besides, binaries have never been packed for add-ons. Here's what to do:

  • Use sshfs to upload .oao files to the new orange.biolab.si server.
  • Use sshfs to get .deb files that contain binaries and make sure they get copied to proper places (see addons.py).
  • Ask Tomaž where Windows binaries can be obtained; make sure those get copied to the .oao files too.

Change History

comment:1 Changed 3 years ago by matija

Add-on packaging now works with sshfs, uploads to the correct server, and the OS does not start the packaging script (and shutdown) by itself; the n9 fires up the script after powering on the VM, then shuts the machine down.

The second and third item on the list still have to be done, though.

comment:2 Changed 3 years ago by matija

Mitar, I thought you said addons are packaged alongside Orange in .deb files, but it seems I misunderstood you. So I have to ask you again: where are add-on binaries for Linux produced so that I can copy them into the .oao files? Specifically, I looking for _orngTextWrapper.so.

(I'll then also want to know where to obtain Mac binaries and I'll ask Tomaž about Windows binaries later.)

comment:3 Changed 3 years ago by matija

  • Status changed from new to accepted

Noting personal correspondence with Mitar: this is not yet done; Debian packaging routines have been done only experimentally. It would be much easier if Orange and each of add-ons was a standard Python package with setup.py; maybe that's what we need to do first.

I have to think about whether we should at least automatically compile Debian binaries for the Text add-on on the add-on packaging VM; that should be easy to do.

comment:4 Changed 3 years ago by mitar

Problem with binaries are dependencies. For example, on Mac OS X it can link with different libraries: Fink's, MacPorts' or system's. Which one of those should be add to .oao files?

Similar problem also exists for Debian? This is also the reason why you probably cannot compile this on add-on packaging VM because you cannot compile (or hardly) for multiple platforms.

comment:5 Changed 22 months ago by matija

  • Status changed from accepted to closed
  • Resolution set to wontfix

Add-ons are now packaged in eggs and uploaded to PyPi. Binaries in add-ons are discouraged; at the moment, only the Text add-on actually has a binary part, and it's outdated anyway. Closing this as wontfix.

Note: See TracTickets for help on using tickets.