From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] A patch to add a flag __SKIP_LIST_DEPS_LUA
Date: Mon, 18 Jan 2021 18:20:19 +0900 [thread overview]
Message-ID: <20210118182017.00E4.50F79699@gmail.com> (raw)
In-Reply-To: <878s8sdp6l.fsf@Rainer.invalid>
On Sun, 17 Jan 2021 07:59:14 +0100, Achim Gratz
> Lemures Lemniscati via Cygwin-apps writes:
> > Does it mean that we should have a way to rebase such dynamic objects
> > automatically?
>
> Well, the first step is to make sure that packaged and locally installed
> stuff stays separate (for Perl this is the distinction between vendor
> and site distributions) and set up a sensible precedence order. Next is
> that users might not have admin rights, so there's a separation between
> local system and local user to consider (Perl: local::lib). Once you
> have that sorted then yes, you need to think about when and how to do
> the rebase of any dynamic objects you are going to produce. For Perl I
> managed to insert an automatic ephemeral rebase, but only for i686 and
> packages built with ExtUtils::MakeMaker (so that build tests can
> actually work without having to do an extra step). The local
> installations should be taken care of via the autorebase facilities,
> although that requires cooperation from the system admin for user
> installations.
>
Thank you for comments and advices.
I'll try it.
Regards,
Lem
next prev parent reply other threads:[~2021-01-18 9:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 10:06 Lemures Lemniscati
2021-01-15 20:02 ` Achim Gratz
2021-01-15 23:16 ` Lemures Lemniscati
2021-01-16 6:50 ` ASSI
2021-01-17 1:20 ` Lemures Lemniscati
2021-01-17 6:59 ` Achim Gratz
2021-01-18 9:20 ` Lemures Lemniscati [this message]
2021-02-15 15:12 ` Multiple version of Lua with alternatives Lemures Lemniscati
2021-02-20 7:40 ` Achim Gratz
2021-02-20 10:15 ` Lemures Lemniscati
2021-02-22 22:14 ` Multiple versions " Lemures Lemniscati
2021-02-24 4:18 ` Multiple version " Lemures Lemniscati
2021-02-24 5:20 ` Marco Atzeri
2021-02-24 6:53 ` Brian Inglis
2021-02-24 11:03 ` Lemures Lemniscati
2021-02-24 16:38 ` Brian Inglis
2021-02-27 8:13 ` Lemures Lemniscati
2021-02-27 12:32 ` Achim Gratz
2021-02-28 9:34 ` Lemures Lemniscati
2021-03-01 11:26 ` Lemures Lemniscati
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=20210118182017.00E4.50F79699@gmail.com \
--to=lemures.lemniscati@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).