octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can "Installing Packages" project needs to be done as GSoC project?


From: Juan Pablo Carbajal
Subject: Re: Can "Installing Packages" project needs to be done as GSoC project?
Date: Thu, 25 Apr 2013 14:37:51 +0200

On Thu, Apr 25, 2013 at 5:33 AM, Sai Manoj Kumar Yadlapati
<address@hidden> wrote:
> Hello, I want to participate in GSoC for the Octave project
> "Installing packages". Then, I came to know about the bitbucket
> repository 
> https://bitbucket.org/carandraug/octave/commits/all/13d1e9bfa362/branch("pkg").
> I see that it has some features from OEP:pkg working. So, my question
> is that what else needs to be implemented. I can't read the complete
> code of pkg module right now, as I have exams this week. So, could you
> please tell me what is completed till now and what else is remaining.
> Is the "yet to be implemented" part big enough to be implemented as a
> GSoC project?
>
>
> Thanks
> Sai Manoj Kumar Y.

Not implemented yet:

- install packages from a given url and Argora.
-  Automatic dependency tracking.
- update packages consistently with dependencies.
- support for multi-folder packages (sub-packages, examples: geometry,
ocs, etc..).
- search function doc-strings on installed packages and on given url.
- installing desired version of packages.
- global, local and external.
- working with different package versions

optional:
- interface with a function that does what releasePKG.m in the
Octave-Forge repository, folder admin, does.

I do not know if this is big enough, but there is a lot of work there
if one is going to do it properly.

Cheers






- options to create a package


reply via email to

[Prev in Thread] Current Thread [Next in Thread]