This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Cygport per-package PKG_EXCLUDE?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sat, 3 Aug 2013 20:03:03 +0200
- Subject: Cygport per-package PKG_EXCLUDE?
- Reply-to: cygwin-apps at cygwin dot com
Hi Yaakov,
I'm not quite happy with the monolithic packaging of my new pl package.
I'd like to create a package structure similar to the Fedora packaging.
I'm just struggling with the complicated file structure which leads to
pretty complicated PKG_CONTENTS strings.
So I was wondering, if cygport couldn't implement some sort of per-package
PKG_EXCLUDE technique, analogue to the %exclude directive in rpm spec
files. For instance, consider a directory with lots of files, of which
only 2 or so shall be packaged separately.
Instead of complicated glob expressions like this:
PKG_NAMES="foo bar baz"
foo_CONTENTS="usr/bin/[ac-z]* \
usr/bin/b[b-z]*"
usr/lib/foo/[ac-z]* \
usr/lib/foo/b[b-z]*"
bar_CONTENTS="usr/bin/bar usr/lib/foo/bar"
baz_CONTENTS="usr/bin/baz usr/lib/foo/baz"
you could write:
PKG_NAMES="foo bar baz"
foo_CONTENTS="usr/bin usr/lib/foo"
foo_EXCLUDE="usr/bin/bar usr/bin/baz usr/lib/foo/ba*"
bar_CONTENTS="usr/bin/bar usr/lib/foo/bar"
baz_CONTENTS="usr/bin/baz usr/lib/foo/baz"
This is a simple example. pl.spec from the Fedora pl package is a bit
more complicated.
Would that be very tricky to implement?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat