From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Building from source packages
Date: Wed, 18 May 2016 16:05:00 -0000 [thread overview]
Message-ID: <20160518160534.GD361@calimero.vinschen.de> (raw)
In-Reply-To: <e04b604a-3e2a-80b2-5653-b1eeac1ae395@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On May 13 15:33, Jon Turney wrote:
>
> Recently I've done a little prototyping of a system to build from uploaded
> source packages in a VM, to verify that they recreate packages with the same
> contents as the uploaded packages.
>
> Issues I noted were:
> [...]
> * a handful of packages are oddities
>
> These often contain source and patches, but no build script, so the
> configuration used by the maintainer to build the package isn't recorded (at
> least in a way accessible to automation)
>
> pkg ver arch
> --- --- ----
> bzr 2.6+b2-2 x86 contains source for 2.6b2-1 and 2.6+b2-2
> exim 4.86-1 both
> fetchmail 6.3.21-1 x86
> flex 2.5.39-1 both orphaned
> ipc-utils 1.0-1 x86
The orignal x86 package predates me using cygport. The x86_64 package
has then probably been built by Yaakov, who's much less a slacker than
I am. Just rebuilding the 32 bit packafge with Yaakov's 64 bit
cygport file will probably do.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-18 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 14:33 Jon Turney
2016-05-13 19:44 ` Andrew Schulman
2016-05-23 13:54 ` Jon Turney
2016-05-14 7:23 ` Achim Gratz
2016-05-18 16:05 ` Corinna Vinschen [this message]
2016-05-18 16:32 ` Marco Atzeri
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=20160518160534.GD361@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).