public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
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: Sat, 16 Jan 2021 08:16:24 +0900	[thread overview]
Message-ID: <20210116081623.C2D8.50F79699@gmail.com> (raw)
In-Reply-To: <87mtxarmsu.fsf@Rainer.invalid>

On Fri, 15 Jan 2021 21:02:25 +0100, Achim Gratz
> Lemures Lemniscati via Cygwin-apps writes:
> > This is a fixed patch for cygport:
> >
> > I'd like to apply alternatives to lua packages to have different
> > versions of lua being installed. But, in such cases, current
> > __list_deps() might pick wrong dependencies.
> >
> > And, this is a patch to add a flag __SKIP_LIST_DEPS_LUA to skip
> > __list_deps() detecting depedency on lua, for the time being.
> 
> Your patch is overshooting your goal I'd think.  What you likely want
> instead is to specify which lua to use in setting up the luapaths
> variable so that the correct dependencies get extracted.
> 
> > I think it will do no harm.
> 
> For a more general facility of suppressing unwanted dependencies see:
> 
> https://repo.or.cz/cygport/rpm-style.git/commitdiff/83b4df817b81fe39257e59fe882b76ca18a80d7c
> https://repo.or.cz/cygport/rpm-style.git/commitdiff/d447a7553d93390f7eb3814216640ea6a2afdd4a
> 
> I needed this specifically for being able to split the perl_base package
> off perl and switching from manual to automatic generation of the
> dependency on the perl5_0xy provide.

Thank you, Achim.

I think it is what I'm longing for.
And it works.



What I'd like to do is to have both lua5.3 and lua5.4 be installed, and
alternatives make a symbolic link to lua5.3 or lua5.4  (new packages
lua5.3-5.3.6-1 and lua5.4-5.4.2-1 which I try packaging.
And I'm trying to package luarocks for lua5.3 and lua5.4
(lua5.3-luarocks and lua5.4-luarocks) by a single cygport file.

Regards,

Lem


  reply	other threads:[~2021-01-15 23:16 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 [this message]
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
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=20210116081623.C2D8.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).