[Octave-bug-tracker] [bug #58487] pkg update should be able to update external packages

[Andrew Janke]

Follow-up Comment #1, bug #58487 (project octave):

Instead of having the individual packages point back to a canonical
distribution point from their DESCRIPTION, maybe this could be done by
defining a CSV or JSON format where a repository (like Octave Forge or a
third-party repo or package index) could list all the packages and versions
they contain? That way you could create repos that archive and publish
distributions of packages even if the packages themselves do not internally
declare themselves to be distributed from that location. Then a `pkg` user
could register multiple repositories in addition to Octave Forge, and it
wouldn't require the package distributions themselves to know about those
repositories. (Like how Homebrew allows you to define custom Taps.) And it
would support relocating the repository/index locations to different URLs
without breaking the references in existing versions of the package archive
files.

I think there was a discussion on this about a year ago (where I was asking to
get a little richer package index metadata from Octave Forge for Packajoozle's
use), but I can't find the relevant bug for it now.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58487>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/