Re: cygport: Adding arbitrary files to the src package

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

Hi Marko,

On May  7 13:36, marco atzeri wrote:
> On 5/7/2012 12:33 PM, Corinna Vinschen wrote:
> >Hi Yaakov,
> >
> >
> >assuming I'd like to add some arbitrary files to the source package, so
> >that the -src package looks like this:
> >
> >   foo-3.4.5.tar.bz2
> >   foo-3.4.5-1.cygport
> >   foo-3.4.5-1.cygwin.patch
> >   foo-3.4.5-1.src.patch
> >   arbitrary-file-1
> >   arbitrary-file-2
> >
> >The idea here is that the files are neither part of the sources, nor do
> >I want the files to be part of the patches since they aren't patches.
> >They are just some files which should show up in the source package for
> >some dubious reason of my own.
> 
> 2 possible ways:
> 
> 1) as additional sources as SRC_URI accepts multiples files,
> 
> 2) as dedicated patch as PATCH_URI accept multiple files.
> 
> On lapack I use both the two solutions, for different reason:
> 
> SRC_URI="http://www.netlib.org/lapack/${ORIG_PN}-${PV}.tgz
> http://www.netlib.org/cblas_20110120.tgz
> http://www.netlib.org/lapack/manpages-3.4.0.tgz";
> 
> PATCH_URI="cblas-cmake.patch
> lapack-dll.patch"
> 
> For you case PATCH_URI should be better (IMHO), as first case
> unlikely put the files in the right place and you will need to
> redefine "src_unpack_hook()" plus CYGPORT_USE_UNSTABLE_API=1
> for moving them around.

The problem is, the file is generated during the build.  Nevertheless
it's not supposed to be part of the binary package but part of the
source package.  As far as I can see, if I add it to SRC_URI or
PATCH_URI, cygport will try to unpack or apply it as patch during the
prep stage, but the file won't exist at the time...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat