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: cygport patches for consideration
Date: Tue, 07 Apr 2020 20:11:18 +0200	[thread overview]
Message-ID: <874ktvcgjd.fsf@Rainer.invalid> (raw)
In-Reply-To: <11ecc96f072ada00b135d5a1c3de0c5987f069dc.camel@cygwin.com> (Yaakov Selkowitz's message of "Tue, 07 Apr 2020 13:37:13 -0400")

Yaakov Selkowitz writes:
>> I guess I can change my cygport generator instead to use
>> CPAN_DIR when needed, but haven't got around doing so.
>
> Depending on its size, it would be nice to get this generator into
> cygport's tools, and could possibly be used as the basis for other such
> generators for other languages.

It does a few other things before it gets to generating a cygport file.
It'd probably be a day or two of excising the cygport generation
facility, but again I'd need a round tuit.  But then again who knows
what we might have time for unexpectedly…

> This change would reduce the number of possible dependencies found by
> only looking for those starting at the beginning of a line, which
> should eliminate false positives from perldocs and optional deps.  So,
> yes, some more false negatives, but also much less false positives. 
> When would there be false positives in this case?

I haven't tested it, but it seems that you would pick up conditional
imports that employ the "if" pragmatic module (which is the canonical
way of doing conditional imports).  Short of special-casing the more
common uses of these you're left holding the bag on these anyway since
you simply can't know whether the condition is true without evaluating
the scope.  On the other hand you're now prone to skip imports in BEGIN
blocks, since these would mostly be indented.

>> When looking in setup.log.full…  this output used to go to the console,
>> but got axed quite some time ago.
>
> Most people aren't going to check the log for that, nor does the log
> allow them to do anything about it.

Well, at least it lets them know _if_ they care.

>> > What would make more sense is to have a utility akin to "rpmconf -a"
>> > on RPM-based systems which allows the user to compare existing files
>> > with their /etc/defaults and choose if and how to merge the
>> > differences.
>> 
>> Sure, but that's not cygport's business, no?
>
> No, this would be something separate, or possibly part of cygutils. 
> But's it's not the postinstall's business either AFAIAC.

That's the only good place we have at the moment.  I've built it into
base-files three and a half years ago in case you're wondering.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2020-04-07 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 18:54 Achim Gratz
2020-04-06 14:46 ` Brian Inglis
2020-04-07  0:52 ` Yaakov Selkowitz
2020-04-07 16:52   ` Achim Gratz
2020-04-07 17:14     ` Jon Turney
2020-04-07 17:37     ` Yaakov Selkowitz
2020-04-07 18:11       ` Achim Gratz [this message]
2020-05-10  8:58   ` Achim Gratz
2020-05-10 20:46     ` Yaakov Selkowitz

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=874ktvcgjd.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).