From: Achim Gratz <Stromeko@Nexgo.DE>
To: cygwin-apps@cygwin.com
Subject: Re: Building from source packages
Date: Sat, 14 May 2016 07:23:00 -0000 [thread overview]
Message-ID: <nh6jon$fs6$1@ger.gmane.org> (raw)
In-Reply-To: <e04b604a-3e2a-80b2-5653-b1eeac1ae395@dronecode.org.uk>
Am 13.05.2016 um 16:33 schrieb Jon Turney:
> Out of the 3135 cygported packages for x86, only 175 set DEPEND.
>
> I don't know how we can ensure DEPEND contains accurate information
> without some sort of build service which tests that it does.
That's the trouble exactly. There is no way to find out if your build
dependencies are complete short of starting with a base installation and
then adding them one-by-one. So far I've typically only added
dependencies when the build would otherwise succeed anyway (due to
alternatives picked up in configury).
> Also, there's probably room here for some policy on what is and isn't
> required in DEPEND i.e. packages essential for building, which are
> already dependencies of cygport, probably don't need to be listed.
> Additionally, some cygclasses probably imply additional build
> dependencies, i.e. 'inherit gnome' implies gnome-common is a build-dep,
> etc.
That will occasionally fall flat on its face when the dependencies of
those tools themselves change, but then it is hard to figure out what
the actual dependencies are unless you try to build manually, see above.
> Further, turning DEPEND into a list of cygwin packages to install can be
> complex (e.g., if it contains some pkgconfig atoms, it requires
> knowledge of the files contained in all packages to find the one which
> contains a particular .pc file).
Isn't that what cygcheck does? What's missing is a record of all files
read during the build from the installation.
> A few packages mistakenly use DEPENDS rather than DEPEND, which is
> silently ignored
>
> pkg maintainer
> --- ----------
> cloog-isl Achim Gratz
> isl Achim Gratz
> mpclib Achim Gratz
Heh. I'm pretty sure I've inherited the packages that way... I'll try
to remember that these need cleanup.
--
Achim.
(on the road :-)
next prev parent reply other threads:[~2016-05-14 7:23 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 [this message]
2016-05-18 16:05 ` Corinna Vinschen
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='nh6jon$fs6$1@ger.gmane.org' \
--to=stromeko@nexgo.de \
--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).