Difference between revisions of "Code sprint: pkg.m"

From Octave
Jump to navigation Jump to search
Line 11: Line 11:
 
= Schedule =
 
= Schedule =
 
The code sprint will take place on November 17th and 18th
 
The code sprint will take place on November 17th and 18th
 +
 +
== Check out Carnë's repository ==
 +
https://bitbucket.org/carandraug/octave/changesets/tip/..bookmark%28%22pkg%22%29
  
 
= Objectives =
 
= Objectives =

Revision as of 14:47, 17 November 2012

This page is meant to organize and report the efforts to improve pkg.m

Participants

If you want to participate add your signature, your IRC nick or your sourceforge username.

Schedule

The code sprint will take place on November 17th and 18th

Check out Carnë's repository

https://bitbucket.org/carandraug/octave/changesets/tip/..bookmark%28%22pkg%22%29

Objectives

Reverse autoload function

Though is not related with pkg.m, the function autoload can simplify considerably the PKG_* scripts. The idea is to give generate a function that reverses autoload.

Option update should behave as option install

  • It should parse a list of packages and maybe the same flags as install
  • It should not stop updating if a package is not found (i.e. user local package, not in Forge).

Coders

  • KaKiLa 04:42, 1 November 2012 (PDT)

Integrate generate_html into Octave-core

  • The system used to generate pakage releases should be more closely integrated with the package manager
  • Maybe a "pkg release" command possibly with "pkg release -binary" option would be a good interface

Coders

  • cdf

Keep sources in installed packages

  • "pkg rebuild" should re-generate any .oct files, this would be useful when an Octave update breaks the API

Coders

Remove -global and -local flags

  • Those flags are have shaky functionality so they should disappear

Coders

  • Carnë has already a changeset for this

Allow packages to deprecate functions

  • Create a system that allows packages to deprecate functions as in core. Possibilities are:
    • Get pkg to accept a deprecated directory inside the package and add it to the search path. Functions in those directories would have to be treated the same as the ones inside the core deprecated
    • PKG_ADD can be used to hack this. Package developers would still have to actually write the warnings on the function code but this would allow to have the functions in a separate directory so they don't foget to remove them on the next release
    • The package developer can also use something like Make to create a normal package from something that actually had a more complex structure, inclusive deprecated directories

Coders

Resolve packages dependencies automatically. Download and install

  • Get pkg to resolve dependencies automatically by downloading and installing them too.

Coders

Allow download and install of multiple versions of the same package

Coders

Make pkg.m more verbose by default

  • make the package just a bit more verbose by default

Coders

Support for more than one src directory(?)

Coders

Accept make flags

  • make pkg able to supply extra configure and make flags, useful for distributions, including -j for make

Coders

Remove auto option

Coders

Allow installation from given url

  • Accept -url <url> to install files and packages directly from the web

Coders

Add where is functionality

pkg describe pkg_name gives useful information. But we should allow for more direct queries like

  • pkg whereis function_name
    list the installed packages (loaded or not) that have a function matching the name function_name.
  • pkg whereis -forge function_name
    list all forge packages that have a function matching the name function_name.

Coders

  • KaKiLa