From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Mailing List: CygWin-Apps <cygwin-apps@cygwin.com>
Subject: Re: [ITP] astrometry.net-0.38-1
Date: Wed, 09 Nov 2011 23:24:00 -0000 [thread overview]
Message-ID: <4EBB0BA5.3010508@cwilson.fastmail.fm> (raw)
In-Reply-To: <CAH7za-B6O-fd85R4560uBa0fKt5TJuVAmdabNEDcMyTD2Bpxqw@mail.gmail.com>
On 11/9/2011 5:00 AM, Jussi Kantola wrote:
> AstroTortilla is fine with a custom repo. All we ever wanted was to
> be able to install astrometry.net with Cygwin's setup.exe
OK.
> How many
> would we need for it to be considered significant enough?
No idea.
> Is this document still valid?
> http://sourceware.org/cygwin-apps/package-server.html
Seems accurate -- but it's missing information about gpg security. I
think you want "Creating a custom Cygwin package server" -- you probably
don't want to create or host a full mirror.
> Anything else I need to know?
Here's what I do, locally:
<top>/setup.exe
<top>/genini
<top>/release/foo/foo-1.2.3-1.tar.bz2
<top>/release/foo/foo-1.2.3-1-src.tar.bz2
<top>/release/foo/setup.hint
$ cd cygwin
$ ./genini --recursive release > setup.ini
$ bzip2 -c < setup.ini > setup.bz2
Then, upload setup.ini, setup.bz2, the new tarballs and setup.hint to
your website, replicating the directory structure (from <top>/ on down).
Now, your users will have to invoke setup.exe with the -X, because
otherwise setup.exe will expect the setup.ini/bz2 files to be signed.
However, turning the security measures off is a problem, because then
your users have no protection against corrupted files on the *main*
mirrors, either.
So, ideally, you would ALSO sign *your* setup.ini/setup.bz2 files. See
http://www.cygwin.com/ml/cygwin-announce/2008-08/msg00001.html
Now, this still requires your end users to take an explicit action (see
item (3i),(3ii),(3iii) in the referenced announcement.) You could
enable them to do (3i) or (3iii) via a batch file that you
distribute...or...
See the cygwin-ports instructions for their users, here:
http://sourceware.org/cygwinports/
In that case, the use of 'cygstart' implies that cygwinports would be
*added* to an existing cygwin installation; hence a bare-windows
installation would require two separate setup.exe runs (*). This is
actually a /good/ thing, because it means there's no confusion between
"the standard cygwin installation on my box" and "the cygwinports cygwin
installation on my box" -- your end users would just have one, to which
they've added the "extra" stuff.
(*) future "update" runs of setup would handle both the 'standard'
packages and the addons simultaneously.
> Thanks once again for your time and effort! I'm sorry the lessons you
> gave me will go down the drain if I won't become a package manager ...
> ;-)
You're still managing a package...it just wouldn't be hosted as an
intrinsic part of the cygwin distribution itself.
--
Chuck
next prev parent reply other threads:[~2011-11-09 23:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 8:02 Jussi Kantola
2011-10-04 9:29 ` Corinna Vinschen
2011-10-05 8:43 ` Peter Li
2011-10-05 10:04 ` Jussi Kantola
2011-10-05 16:02 ` Charles Wilson
2011-10-11 10:19 ` Marco Atzeri
2011-10-18 11:21 ` Jussi Kantola
2011-10-18 11:49 ` Chris Sutcliffe
2011-10-18 21:12 ` Ken Brown
2011-10-20 8:19 ` Jussi Kantola
2011-10-30 21:10 ` Jussi Kantola
2011-11-03 12:03 ` Corinna Vinschen
2011-11-03 12:55 ` Charles Wilson
2011-11-03 13:03 ` Corinna Vinschen
2011-11-04 0:52 ` Jussi Kantola
2011-10-05 16:19 ` Andrew Schulman
2011-10-06 13:06 ` Jussi Kantola
2011-10-07 14:20 ` Marco Atzeri
2011-10-07 16:19 ` Jussi Kantola
2011-10-07 16:20 ` Jussi Kantola
2011-10-10 18:54 ` Jussi Kantola
2011-10-10 23:14 ` Christopher Faylor
2011-11-04 6:30 ` Charles Wilson
2011-11-04 9:02 ` Jussi Kantola
2011-11-04 15:12 ` Yaakov (Cygwin/X)
2011-11-04 16:08 ` Charles Wilson
2011-11-04 21:13 ` Charles Wilson
2011-11-07 13:18 ` Jussi Kantola
2011-11-07 14:46 ` Charles Wilson
2011-11-07 16:13 ` Jussi Kantola
2011-11-07 16:18 ` Christopher Faylor
2011-11-08 4:50 ` Charles Wilson
2011-11-08 7:19 ` Christopher Faylor
2011-11-08 12:44 ` Ken Brown
2011-11-09 2:43 ` Chris Sutcliffe
2011-11-09 10:00 ` Jussi Kantola
2011-11-09 23:24 ` Charles Wilson [this message]
2011-11-11 10:46 ` Jussi Kantola
2011-11-11 10:53 ` Jussi Kantola
2011-11-13 17:35 ` Jussi Kantola
2011-11-08 18:01 ` Marco Atzeri
2011-11-08 19:55 ` Christopher Faylor
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=4EBB0BA5.3010508@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--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).