public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Boris Unckel <bu.cygwin@mail.unckel.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin quiet-mode setup against local Repository authentication issue
Date: Fri, 22 Jul 2022 06:48:35 +0200 (CEST)	[thread overview]
Message-ID: <1282714877.945556.1658465315133@email.ionos.de> (raw)
In-Reply-To: <87edyetnh0.fsf@Rainer.invalid>


> Achim Gratz <stromeko@nexgo.de> hat am 21.07.2022 18:55 geschrieben:
> 
> 
> Boris Unckel writes:
> > we plan to have Cygwin distributed with our Softwarecenter package
> > distribution. The process shall not require any user interaction. Due
> > to security policies we don’t grant users direct access to the
> > internet. The mandatory proxy blocks binary downloads. For this reason
> > we have established a JFrog Artifactory remote repository for the
> > whole Cygwin distribution. Accessing this repository by browser works
> > without any issues, both with and without login.
> […]
> > What can we do pass user / password for the –site destination without
> > UI and without user interaction?
> 
> Why do you need user authentication and/or serve the files over HTTP(S)
> instead of just providing a local repository to install from?
> 
> 
> Regards,
> Achim.
> --
The current idea is not to fix the set of available cygwin-packages (and/or versions) in a local copy, neither in the softwarecenter-package, nor in a smb share, but to have the chance of updates with the same softwarecenter-package. Currently the softwarecenter-package contains only the setup.exe plus script. We have several distributions running this way (maven, npm, pypi, conda, rpm...)

Regards
Boris

      reply	other threads:[~2022-07-22  4:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 14:41 Boris Unckel
2022-07-21 16:55 ` Achim Gratz
2022-07-22  4:48   ` Boris Unckel [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=1282714877.945556.1658465315133@email.ionos.de \
    --to=bu.cygwin@mail.unckel.net \
    --cc=cygwin@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).