public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: setup and colons in filenames
Date: Fri, 27 Oct 2017 13:44:00 -0000	[thread overview]
Message-ID: <2b48d6e4-fcde-e0eb-8f67-4269f15a5ef5@dronecode.org.uk> (raw)
In-Reply-To: <8760b0ho0h.fsf@Rainer.invalid>

On 27/10/2017 11:40, Achim Gratz wrote:
> Corinna Vinschen writes:
>> It would be pretty neat if genini could be simplified(*), so a mortal user
>> can just run it with a directory as parameter and it creates a setup.ini
>> file at the top-level of that dir without too much complaining about
>> missing sources etc.

I've worked on [1] a bit so it now contains some instructions how to do 
this, rather than the previous state of affairs, which was "genini 
exists, work it out yourself"

[1] https://cygwin.com/package-server.html#overlay

>> (*) Or better: A user version of calm, packaged in the distro.

Um, we have had this for a while [2], mksetupini is the tool to use if 
you don't need all the extra stuff which calm does.

[2] https://cygwin.com/ml/cygwin-apps/2016-07/msg00047.html

I guess mksetupini could have more friendly defaults to make the command 
lines in [1] shorter if that really scares people off (e.g. default 
--inifile to stdout, --releasearea to '.' and to 
--okmissing=required-package (then need a way to turn it back on, though))

> For better or worse, genini is dead and replaced by mksetupini.  The
> latter is way more picky with having the correct hint files around and
> often refuses to create a setup.ini if it finds something it doesn't
> like.

Not dead, just resting.  Until someone patches it to understand pvr.hint 
files.

I make no apologies for mksetupini being more strict, though.

  reply	other threads:[~2017-10-27 13:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 15:50 Ken Brown
2017-10-25 19:23 ` Jon Turney
2017-10-25 20:16   ` Corinna Vinschen
2017-10-25 20:36     ` Jon Turney
2017-10-25 21:00       ` Corinna Vinschen
2017-10-26 16:14         ` Jon Turney
2017-10-26 16:14   ` Jon Turney
2017-10-26 17:04     ` Ken Brown
2017-10-26 17:20       ` Jon Turney
2017-10-26 17:42     ` Achim Gratz
2017-10-26 17:49       ` Jon Turney
2017-10-26 18:25         ` Achim Gratz
2017-10-27  8:47           ` Corinna Vinschen
2017-10-27 10:40             ` Achim Gratz
2017-10-27 13:44               ` Jon Turney [this message]
2017-10-27 15:20                 ` Ken Brown
2017-10-27 16:28                   ` Corinna Vinschen
2017-10-27 13:43           ` Jon Turney

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=2b48d6e4-fcde-e0eb-8f67-4269f15a5ef5@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).