public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] A patch to add a flag __SKIP_LIST_DEPS_LUA
Date: Sat, 16 Jan 2021 07:50:52 +0100	[thread overview]
Message-ID: <877dodbcj7.fsf@Otto.invalid> (raw)
In-Reply-To: <20210116081623.C2D8.50F79699@gmail.com> (Lemures Lemniscati via Cygwin-apps's message of "Sat, 16 Jan 2021 08:16:24 +0900")

Lemures Lemniscati via Cygwin-apps writes:
> 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.

Multi-version installations are not well supported by setup or cygwin
yet, but the alternatives anyway only address the question of how to set
the default version for the user.  For building packages you'd need to
specify which version to use each time you build something, so any
occurences of plain "lua" (from PATH) would need to be replaced with the
expansion of some variable that would be set appropriately when entering
pkg_info.

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

The packages should be named lua53-luarocks and lua54-luarocks (no dot
in the version number), like OpenSUSE (they seem to be the only
distribution with a multi-version lua and that particular naming scheme
you've chosen).

A different question is if you really want to package this particular
feature.  Just like all the other "package managers" that come with a
specific language or interpreter I'd expect this one to need (maybe
extensive) modifications to work correctly on Cygwin, especially if it
ends up building dynamic objects.  That's one reason I discourage the
use of CPAN on Cygwin, since folks tend to shoot themself into the foot
more often than not by using it.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2021-01-16  6:51 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 [this message]
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=877dodbcj7.fsf@Otto.invalid \
    --to=stromeko@nexgo.de \
    --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).