X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=PNeRgO0UHDm/OUIPGHvyomOm32xeU
	C4GJfcNG5M3/vasPzWcnR9fveOvsgpGr1IcDiPglB1QPrNnultRI3OktuPmUKje5
	UdaVc8JgjfggtnV1pA9yuzIStyTXZ/w5vxSdoFb5tDz9qA+8sUkQ9wajOZlCIJgX
	h6neDz8vGQzZy4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=Omd+wPugqN999IWgRDYKi5FqqhY=; b=O4k
	QhEMMDG3DKShu/JF6TBA9zUUKVt7ZfTdi/0nEMdCRU/5KNDhz1fHTe47x52aPfc6
	rWPvqzc/f2OFKvk6IA2VCdc3jJVQ99nGORYvCQAWzCy1zzfESrc7VHltpAlRKFVa
	58YpvRUXdHcnvfOD/N0qmNtvFa6kge06ajEn7pmI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=3.6 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.2
X-HELO: mail13.admin.ch
From: <Jonas DOT Hagen AT metas DOT ch>
To: <marco DOT atzeri AT gmail DOT com>, <cygwin AT cygwin DOT com>
Subject: RE: Octave package database update
Date: Thu, 27 Feb 2014 15:54:48 +0000
Message-ID: <8AEE65C709C1E74794BEE8AE0C87E0EBC0F4B6@metasmx05.ad.metas>
References: <8AEE65C709C1E74794BEE8AE0C87E0EBC0F07A AT metasmx05 DOT ad DOT metas> <530E3654 DOT 9040407 AT gmail DOT com>
In-Reply-To: <530E3654.9040407@gmail.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-TM-AS-MML: disable
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s1RFt87k015369

On 26/02/2014 19:46, Marco Atzeri <marco DOT atzeri AT gmail DOT com> wrote:
>On 26/02/2014 14:26, Jonas DOT Hagen AT metas DOT 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