Takashi Yano wrote: Furthermore, you do not need to add ffmpeg to "REQUIRES" because
the cmus package itself does not really depend on ffmpeg package
even though it depends libavcodec, libavformat, libavutil and
libswresample.
I was already told once that I probably can leave REQUIRES out.

Currently I'm using it for setting up a minimal test environment where I
install only the packages listed in REQUIRES.
Can cygport give me that information if I do not write any REQUIRES?
Last time I asked the answer was no, and thus I decided to keep it to
ease testing on my side.

Without REQUIRES line, "cygport cmus all" with above patch gives me:
....
cmus requires: cygwin libao4 libavcodec61 libavformat61 libavutil59 libcddb2 libcdio18 libcdio_cdda2 libdiscid0 libFLAC12 libiconv2 libmad0 libmodplug1 libmpcdec7 libncursesw10 libopusfile0 libpulse0 libswresample5 libvorbisfile3 libwavpack1

I guess this is as you expect (if libav* are free from clang dependency),
isn't it?


Yes, it looks good.

I'll drop the REQUIRES the next time I'll upload a package then.


Hello, I have a feature request/question for the cygport maintainer (not sure how those are normally handled)

cygport reports the required packages, but only after building the application.

My workflow is normally the following one:

Setup the cygwin environment for building and testing, download the sources, then in an offline environment, build and test.

Since "cygport cmus all" reports the required dependencies only after building, I have some difficulties in taking advantage of the listed packages...

I could imagine to have a "minimal cygwin environment" for executing "cygport cmus enlist-dependencies", and from the output create one cygwin environment for building, and one for testing, but if it needs to build the application, I do not see how to use it for bootstrapping an offline environment.

I could move the REQUIRES from the cygport file to somewhere else and use it only myself, but at that point, why not use the REQUIRES?

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

Reply via email to