From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84374 invoked by alias); 23 Jul 2016 06:02:05 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 84360 invoked by uid 89); 23 Jul 2016 06:02:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=91, constrain, synchronize, 1151 X-HELO: mail-wm0-f66.google.com Received: from mail-wm0-f66.google.com (HELO mail-wm0-f66.google.com) (74.125.82.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sat, 23 Jul 2016 06:01:54 +0000 Received: by mail-wm0-f66.google.com with SMTP id o80so8679073wme.0 for ; Fri, 22 Jul 2016 23:01:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=bpS/A1VwZm7o4QOQWp4lGsmxJHxWPSwtrTbpvxCcg0I=; b=L4CIl8ShNh4EKhQvx3OAdljrJhHqxMOxX+guNlzS3xbvJmt3PhVSgG/MOydVuAKOTH k+wbakPNfUPgyCknLeF0M7CE/gkbt4rdLeWhfsdNsvU8he1BGsvxDWfXmMrb0NcjMvqC diuBH4OUdO7seNqYAXLjF/M7L/9R+n2sXoyPwnavu2NQcB3aAr/lqIoVGn6Bt8q0goqr OOKFTZgqhyrnGyUj5Q9bHAa92ppAgAba5WIogFxeAiqV3/p6ArC0v2e0MBQQEgLkdxNj MGbhbsQfaRYmsMuyrpfpLOzD+ZRTPuOz6d1nMAjFn3h6sNALh3MVEs9i6tllNg4dUj5Y bMSw== X-Gm-Message-State: AEkoouvFLe+SNjM0zktcggQLp0qy8nTinw+O56K6VzUAtDsodI29xL1biREMB7wpKA3/gg== X-Received: by 10.194.73.136 with SMTP id l8mr4443662wjv.153.1469253710833; Fri, 22 Jul 2016 23:01:50 -0700 (PDT) Received: from [192.168.2.109] (p5B298E5D.dip0.t-ipconnect.de. [91.41.142.93]) by smtp.googlemail.com with ESMTPSA id t188sm15857619wme.19.2016.07.22.23.01.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 23:01:50 -0700 (PDT) Subject: Re: [ITP] FUSE 2.8 To: cygwin-apps@cygwin.com References: <20160718081931.GE7018@calimero.vinschen.de> <20160719094102.GP7018@calimero.vinschen.de> <20160720085223.GV7018@calimero.vinschen.de> <20160722075926.GF7018@calimero.vinschen.de> <3e95a007-7c68-0e06-3779-4e20a3f5291e@gmail.com> From: Marco Atzeri Message-ID: <4279d649-4e3f-a295-46d0-3d39bee15428@gmail.com> Date: Sat, 23 Jul 2016 06:02:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2016-07/txt/msg00072.txt.bz2 On 23/07/2016 02:31, Bill Zissimopoulos wrote: > On 7/22/16, 12:57 PM, Marco Atzeri wrote: > > >> On 22/07/2016 19:58, Bill Zissimopoulos wrote: >>>> winfsp-fuse is a reasonable name. >>>> dokan-fuse also (IMHO) >>> >>> In the interest of moving things forward, I am happy to rename the >>> package. Is it possible for a package with a name winfsp-fuse to >>> satisfy a >>> “fuse” dependency? >> >> It is not clear to me what you mean. >> >> If some package depends on winfsp-fuse, the dependency will be >> winfsp-fuse. >> >> winfsp-fuse will require the external package winfsp. > > My apologies for not making it clearer. What I meant to say is this: > > Suppose I have a package XYZ that requires FUSE. Is it possible that the > “FUSE” dependency can be satisfied by either winfsp-fuse or dokan-fuse? > > If that is not possible it looks like we would have to have winfsp-sshfs > or dokan-sshfs, etc. which IMO is less desirable. > > Bill It depends on the type of dependency - The hard coded dependency is based on dll's example : octave dll requires the readline dll provided by the package libreadline7 $ cygcheck /usr/bin/cygoctave-3.dll |grep readline E:\cygwin64\bin\cygreadline7.dll $ cygcheck -f $(cygpath -u 'E:\cygwin64\bin\cygreadline7.dll') libreadline7-6.3.8-1 In this case the dependency is hard coded in the octave binary itself. We don't have a way (yet) to provide the same dll from two different packages. In theory it can be done with pre/prost install scripts that copy and remove dll's in "/usr/bin" but it will be tricky. We can not use links with dll's on cygwin for windows loader constrain. - The dependency is based on command ls -l /usr/bin/automake lrwxrwxrwx 1 marco Administrators 34 Aug 3 2013 /usr/bin/automake -> /usr/share/autotools/am-wrapper.sh 64 $ cygcheck -f /usr/share/autotools/am-wrapper.sh automake-9-1 $ cygcheck -cd |grep automake automake 9-1 automake1.10 1.10.3-2 automake1.11 1.11.6-2 automake1.12 1.12.6-2 automake1.13 1.13.4-1 automake1.14 1.14.1-2 automake1.15 1.15-1 automake1.4 1.4p6-11 automake1.5 1.5-11 automake1.6 1.6.3-12 automake1.7 1.7.9-11 automake1.8 1.8.5-11 automake1.9 1.9.6-11 automake is a wrapper package that can be defined to match the needed version and pull all the versions $ automake --version automake (GNU automake) 1.14.1 $ cygcheck-dep -r automake automake: requires ( automake1.10 automake1.11 automake1.12 automake1.13 automake1.14 automake1.15 automake1.4 automake1.5 automake1.6 automake1.7 automake1.8 automake1.9 bash gawk ) Alternatives can also be used to manage command dependency $ alternatives --display unison unison - status is auto. link currently points to /usr/bin/unison-2.48 /usr/bin/unison-2.48 - priority 2048 Current `best' version is /usr/bin/unison-2.48. specially when you need only one variant installed, but several are potentiall available: $ cygcheck -cd |grep unison unison2.48 2.48.3-2 $ cygcheck -p "bin/unison-" Found 7 matches for bin/unison- unison2.27-2.27.157-4 - unison2.27: Synchronize ... unison2.32-2.32.52-4 - unison2.32: Synchronize ... unison2.40-2.40.102-1 - unison2.40: Synchronize .. unison2.45-2.45.28-1 - unison2.45: Synchronize .. unison2.48-2.48.3-1 - unison2.48: Synchronize .. unison2.48-2.48.3-2 - unison2.48: Synchronize .. unison2.49-2.49.543-1 - unison2.49: Synchronize .. Regards Marco PS: today there is only one case of packages providing same name dll's and the solution is sub-optimal and working only as - there is a preferred order openblas cygblas-0.dll is preferred versus lapack one. - the maintainer is the same: me More packages with the same dll collision will require to work on pre/prost install scripts general solution.