From: Jon Turney <jon.turney@dronecode.org.uk>
To: Federico Kircheis <federico@kircheis.it>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: nnn
Date: Fri, 14 Oct 2022 17:35:27 +0100 [thread overview]
Message-ID: <7eedd556-7f4d-b006-713f-917efdca79bd@dronecode.org.uk> (raw)
In-Reply-To: <11bd75e2-eccd-e07d-5932-e156fe7147b8@kircheis.it>
On 13/10/2022 20:11, Federico Kircheis wrote:
> On 10/10/2022 15.02, Jon Turney wrote:
>> On 09/10/2022 14:54, Federico Kircheis wrote:
>>
>>> REQUIRES="libncursesw10 libreadline7"
>>
>> It looks like these dependencies are successfully auto-detected, so
>> you don't need to explicitly list them.
>
> Does cygwin/cygport offer some functionalities for querying those if not
> written in the cygport file?
>
> Currently I "parse" the file for creating automatically a test environment.
> Removing those means that I am not currently able to recreate such
> environment automatically, and would need to track the information
> separately.
That information is written into the requires: line of the generated
.hint (e.g. nnn-4.6-1.x86_64/dist/nnn/nnn-4.6-1.hint)
Ideally we'd have some mode of setup where you could write e.g setup -P
./nnn-4.6-1.tar.xz and it would install that just built package and it's
dependencies, but SHTDI.
(https://cygwin.com/packaging-contributors-guide.html#installing
somewhat discusses this lack...)
prev parent reply other threads:[~2022-10-14 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:54 nnn Federico Kircheis
2022-10-10 13:02 ` nnn Jon Turney
2022-10-13 19:11 ` nnn Federico Kircheis
2022-10-14 16:35 ` Jon Turney [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=7eedd556-7f4d-b006-713f-917efdca79bd@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=federico@kircheis.it \
/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).