public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Packaging Perl
Date: Thu, 04 Jun 2020 21:22:32 +0200	[thread overview]
Message-ID: <87367ar5zb.fsf@Rainer.invalid> (raw)
In-Reply-To: <d1651065-784e-d5be-15ed-8c9c184e785c@dronecode.org.uk> (Jon Turney's message of "Thu, 4 Jun 2020 19:50:47 +0100")

Jon Turney writes:
> I think the perl cygclass in cygport can know the perl version being
> built against, and can add that to the requires?

It knows the Perl version and can infer what the provide should be, yes.

But for the provides to be useful in a broader sense I think we need to
come up with a plan on how to record which provide(s) are present in the
current installation (given that the installation might be so old by the
time it gets upgraded that the current setup.ini doesn't have that bit
of information anymore).

> I'm not sure doing it automatically for everything is possible.

It sure is, the question is how to get it into the installation with the
least amount of changes.  To that end, I think we'd need to plop
something into the file system somewhere.  I believe the plan was that
provides do not create (empty) tar files or show up in the package
archive, but are purely metadata on the repository side, so that'd be
something that setup.exe would have to do.  It might be possible to
stuff it into installed.db, maybe even without changing the format
version, but I'm not sure that'd work for all scenarios.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

      reply	other threads:[~2020-06-04 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 10:23 Achim Gratz
2020-06-04 18:50 ` Jon Turney
2020-06-04 19:22   ` Achim Gratz [this message]

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=87367ar5zb.fsf@Rainer.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).