public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
Subject: Re: Questions on package adoption conventions
Date: Fri, 30 Oct 2015 23:25:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.63.1510301617550.16734@m0.truegem.net> (raw)
In-Reply-To: <5633EA0E.6030106@gmail.com>

Thanks Marco.

On Fri, 30 Oct 2015, Marco Atzeri wrote:
> On 30/10/2015 22:48, Mark Geisert wrote:
>> Q3: What kind of external access is typically used for hosting final
>> builds?  I've run a micro-ISP that allowed on-request FTP access, by IP
>> address, to customers, but have not needed to run anonymous FTP to this
>> point.  What about SSH/SFTP?  Is there such a thing as anonymous SFTP?
>> Does HTTP and/or HTTPS access need to be provided?
>
> Upload instructions:
> https://sourceware.org/cygwin-apps/package-upload.html

D'oh, users download source packages from cygwin.com, of course.

I was confused by the SRC_URI= line in cygutils.cygport.  Does that merely 
indicate where this package came from at the time the .cygport file was 
written, or does it denote a commitment by the maintainer to continue 
hosting the package from that URI?  If the latter, that's why I was asking
about access methods.  Is SRC_URI required?

..mark

  reply	other threads:[~2015-10-30 23:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 21:48 Mark Geisert
2015-10-30 22:07 ` Marco Atzeri
2015-10-30 23:25   ` Mark Geisert [this message]
2015-10-30 23:59     ` Marco Atzeri
2015-10-31  0:18     ` Jon Turney
2015-10-31 16:03       ` Corinna Vinschen
2015-11-01  4:15         ` Mark Geisert
2015-11-02  9:29           ` Corinna Vinschen
2015-11-04 11:36             ` Mark Geisert
2015-11-04 12:08               ` Corinna Vinschen
2015-11-04 18:48               ` Achim Gratz

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=Pine.BSF.4.63.1510301617550.16734@m0.truegem.net \
    --to=mark@maxrnd.com \
    --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).