This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Octave package database update
- From: <Jonas dot Hagen at metas dot ch>
- To: <marco dot atzeri at gmail dot com>, <cygwin at cygwin dot com>
- Date: Thu, 27 Feb 2014 15:54:48 +0000
- Subject: RE: Octave package database update
- Authentication-results: sourceware.org; auth=none
- References: <8AEE65C709C1E74794BEE8AE0C87E0EBC0F07A at metasmx05 dot ad dot metas> <530E3654 dot 9040407 at gmail dot com>
On 26/02/2014 19:46, Marco Atzeri <marco.atzeri@gmail.com> wrote:
>On 26/02/2014 14:26, Jonas.Hagen@metas.ch wrote:
>> Shouldn't the package database update be done at
>> installation time of the package from the Cygwin setup,
>> rather than on every start of octave?
>> The setup has the right privileges to do so. Also, this would
>> make octave to start faster.
>
>unfortunately it will create more problem than current solution, and the
>boot check is very fast.
>
>Current solution checks if the package database is older that the
>package directory and only in that case update the database.
>Drawback you need the setup permission.
>
>See
>/usr/share/octave/site/m/startup/octaverc
>
>If I put the update script on every forge package, and you
>install 10 (or 50 packages) it will require to start for every package
>octave, update the database and close.
>Doing so, the she setup could be very slow and it could likely fail
>for fork issue as octave is very large and need to lot a lot of directories.
I do not agree here, for two reasons:
Firstly I do not expect a setup to be fast. I expect it to set up everything
and make it ready to use. I have spent a few hours until I found out how
to solve this issue. A few minutes more for the setup would not hurt.
Secondly, wouldn't it be possible to make a postinstall script, that makes the
database update? This could be the same for each package, either with the
same date-check as you have now in octaverc or with the same name for all
the packages.
As far as I understand Cygwin, the postinstall scripts are executed after _all_
the packages have been installed?!
This would ensure that the database is only updated once, even if a lot of
Octave packages have been installed.
>Worst if you remove everything the post install script could try to run
>without octave and failing all the time.
Yes of course, the script (shell) would need to check for that.
>Could you check if changing permission with
>
>chmod 666 /usr/share/octave/octave_packages
>
>the situation improve ?
Yes, this helps if the octave_packages file has already been created.
But as a user, I would appreciate a more convenient solution.
What do you think about the my proposal above? Could it even work?
Thanks for your explanations!
Regards,
Jonas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple