From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn Maintainer] octave
Date: Sat, 30 May 2015 05:13:00 -0000 [thread overview]
Message-ID: <556946DF.3070502@gmail.com> (raw)
In-Reply-To: <87bnh3dw92.fsf@Rainer.invalid>
On 5/29/2015 9:22 PM, Achim Gratz wrote:
>
> The site octaverc has code that tries to keep the package directory
> up-to-date. That's a no-no, since normal users don't have permission to
> change files under /usr/lib.
/usr/share/octave/site/m/startup/octaverc is updating
"/usr/share/octave/packages"
if any subdirectory under "/usr/share/octave/" has been added
or removed, to update the octave package database.
Why do you see actions under "/usr/lib" ?
See note on:
https://sourceware.org/ml/cygwin-announce/2014-08/msg00033.html
> Could you please remove that code and put the update into a post-install
> script?
It is build as such as a normal post-install script will not work.
I will look if I can find a mechanism that allow a common approach for
the 50s octave-* packages.
In the past these problems make another solution impossible:
- the script must run octave and due to octave lib dependency a fork
failures on 32bit was almost guarantee.
- the script must run for any postinstall - postremove of any
octave-* (forge packages). So
1) it will be heavy to run it 50 times, it must be a common one.
2) we have no post remove.
3) If also octave is removed the post remove must not run.
- /usr/share/octave/packages does not exist if the database is empty
so I can not change its permission in the postinstall phase before
its creation.
Regards
Marco
> Regards,
> Achim.
next prev parent reply other threads:[~2015-05-30 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 19:23 Achim Gratz
2015-05-30 5:13 ` Marco Atzeri [this message]
2015-05-30 6:01 ` Achim Gratz
2015-05-30 6:12 ` Marco Atzeri
2015-05-30 6:18 ` Marco Atzeri
2015-06-01 10:05 ` Marco Atzeri
2015-06-01 16:20 ` Achim Gratz
2015-06-22 16:49 ` Achim Gratz
2015-06-22 20:43 ` Marco Atzeri
2015-06-23 5:35 ` Achim Gratz
2015-06-23 6:20 ` Marco Atzeri
2015-06-23 15:32 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=556946DF.3070502@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).