From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Building from source packages
Date: Wed, 18 May 2016 16:32:00 -0000 [thread overview]
Message-ID: <9e467345-d26f-85cc-6283-81af62fd927f@gmail.com> (raw)
In-Reply-To: <e04b604a-3e2a-80b2-5653-b1eeac1ae395@dronecode.org.uk>
On 13/05/2016 16: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
> mined 2015.25-0 x86_64 a note from maintainer pointing to x86 src
> nmh 1.6-2 both uniquely, g-b-s script name doesn't end .sh
> popt 1.16-1 both orphaned
> suite3270 3.3.15ga9-1 both uniquely, multiple g-b-s and one tarfile
flex and popt were probably built with a g-b-s like script by CGF.
I had the same issue when I adopted make.
popt version is last upstream, while
flex had a new release last November after long time
Regards
Marco
prev parent reply other threads:[~2016-05-18 16:32 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
2016-05-18 16:32 ` Marco Atzeri [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=9e467345-d26f-85cc-6283-81af62fd927f@gmail.com \
--to=marco.atzeri@gmail.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).