From: Hanspeter N. <fi...@sn...> - 2012-07-26 14:40:05
|
On 7/26/2012 10:31 AM, Sjors Gielen wrote: > Op 26-07-12 16:06, Alexander Hansen schreef: >> On 7/26/12 6:50 AM, Hanspeter Niederstrasser wrote: >>> Is there a way to copy the tarball from Source2 into a specific dir >>> inside the expanded Source1 tree *without* expanding Source2? >>> >>> A package I'm making needs several auxiliary tarballs, but it checks for >>> the tarball inside %b/external/src and tries to download it >>> automatically if missing. "Source2ExtractDir" doesn't work for this case. >>> >>> Hanspeter >>> >> >> I believe fink tries to expand any tarball listed in a SourceN field. >> You might have to go with a hackish option and "re-tar" the expanded >> Source2 in %b/external/src, since one can't really count on a source >> being in e.g. %b/../../.. . I face this same problem with the Octave >> Forge packages, which insist on being installed from tarballs for >> current Octave versions. > > I think you could try renaming the file (SourceFileRename, or something like that) to get around Fink's file type detection, then move and rename it back in your PatchScript. But that expects knowing where source files are downloaded to, which is not necessarily %p/src. Hanspeter |