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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=C+pnHtpqiOrWrHyEAHbK84ToJ8vGSNhAuVCszUS0VKg
	k6rIFSjgTbp/xlvRD7E05zmPR4mnziknGQ+8qjJdEuEGx6JvV8nJnHTdUwiUNERs
	qM+0mbrhDtMPAjHNYCQ+NzBm7DXXeXJdSxhU3C2Foe8UZwBA+bCWPP7iZw7QYqJc
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=7iJGgAtD8TXKFYlH8JoANjmS2cA=; b=ykD2D3d7dTCG3uWJE
	ENGzhQitfcQUYq6yWtE8f0MZfSOE7fdxLRgMOIWtbi39NfKC2sugSRBwVtcktKLl
	1CIz2ArrNxJh6iqYRzEBN0c/oT3/BX5Qy2YCSHaWHsamESHzFex6V6uDr3t5W0pO
	3aiVOe3h72ApQB8Ut83SXy+Z8U=
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=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-ea0-f182.google.com
X-Received:	by 10.15.90.204 with SMTP id q52mr46400eez.95.1393529187987; Thu, 27 Feb 2014 11:26:27 -0800 (PST)
Message-ID:	<530F9161.9090706@gmail.com>
Date:	Thu, 27 Feb 2014 20:26:25 +0100
From:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Octave package database update
References:	<8AEE65C709C1E74794BEE8AE0C87E0EBC0F07A AT metasmx05 DOT ad DOT metas> <530E3654 DOT 9040407 AT gmail DOT com> <8AEE65C709C1E74794BEE8AE0C87E0EBC0F4B6 AT metasmx05 DOT ad DOT metas>
In-Reply-To:	<8AEE65C709C1E74794BEE8AE0C87E0EBC0F4B6@metasmx05.ad.metas>
X-IsSubscribed:	yes

On 27/02/2014 16:54, Jonas.Hagen metas.ch wrote:
> On 26/02/2014 19:46, Marco Atzeri  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?

> 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.

You missed a point, the update through setup could fail to
start octave. Octave has a very very large list of dll's to load.
I consider it more likely than your case.

I will add a note on README for next octave package,
if I do not find a better solution

>> 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?

At begin, I was thinking something like that, but I dropped it:

- High chance to fail during post install
- problematic behavior during remove
- hard to synchronize
- 1 script only versus more than 50 post-install script


> Thanks for your explanations!
> Regards,
> Jonas

Regards
Marco


--
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

- Raw text -