From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105090 invoked by alias); 26 Jul 2016 12:40:39 -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 104280 invoked by uid 89); 26 Jul 2016 12:40:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Herbert, hersto@gmx.de, herstogmxde, U*hersto X-HELO: mail-yw0-f193.google.com Received: from mail-yw0-f193.google.com (HELO mail-yw0-f193.google.com) (209.85.161.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 26 Jul 2016 12:40:28 +0000 Received: by mail-yw0-f193.google.com with SMTP id r9so597774ywg.2 for ; Tue, 26 Jul 2016 05:40:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=iBsck3sOqz8OKv11aZWmf2jzPH4F8gIXjjVLtt6EbGo=; b=OBKa+gPb+LR++AeIu7p5tsgMyP/bYb87nPSd3TuPsS3EV0YeF8pve/8RRDnSr8lrrz AAUEfWSull4JfnHTxDJTaJ/hIPzq6128SSXu9nbgYo8J1u04EcEuyTLGlTLFhxmCM6bE fb0snJLIAZ1lm+MHGRP17Vz4vxeizUNBgFpjaaum3q5T1cy5+2FYspSVvwQzKKi1wJex Q2/X3vOWC1X8ez/ukN2520ThaQN41zC1sIxRJjASNo1mHHo7pqE2QYUpEn2xXprUqAhR wLQiPA3bhUUWJrzTie91YpO7hriGQex0EXjs3Mq3OXl44FaqOpfAIWZnJV7HsmeZBUDT YZAg== X-Gm-Message-State: AEkoous11LxXuiVOh/6VhO4dLTXoLXFKFJec3WdwQAGxdYcWunlacToEPsSYoqS5ZVbLqRplga1TR6qbtbU/Nw== X-Received: by 10.31.136.70 with SMTP id k67mr10192395vkd.11.1469536826143; Tue, 26 Jul 2016 05:40:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.7.198 with HTTP; Tue, 26 Jul 2016 05:40:25 -0700 (PDT) In-Reply-To: <81992397-64d2-bf0d-a7cd-9620a559a7a4@gmx.de> References: <20160723104021.GA18159@calimero.vinschen.de> <20160723174836.GD11373@calimero.vinschen.de> <20160725073538.GF11373@calimero.vinschen.de> <81992397-64d2-bf0d-a7cd-9620a559a7a4@gmx.de> From: Adrien JUND Date: Tue, 26 Jul 2016 12:40:00 -0000 Message-ID: Subject: Re: [ITP] FUSE 2.8 To: cygwin-apps@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016-07/txt/msg00082.txt.bz2 >You could define a package "fuse" with no contents and a dependency on >package "winfsp-fuse". Then later when/if another FUSE implementation >becomes available, "somebody" could replace the "fuse" package with >whatever is required to get alternatives support for the variants. I have not officially open request now but right after we found a solution to handle fuse wrapper packages, I will apply for dokan as well as winfsp. Also, I think that packages binary dependent to a fuse wrapper would not work if it is another wrapper that is installed. So shall we not just let the package dependent to fuse, explicit the wrapper that he will use ? 2016-07-26 10:45 GMT+02:00 Herbert Stocker : > Hi all, > > On 7/26/2016 8:27 AM, Mark Geisert wrote: >> >> You could define a package "fuse" with no contents and a dependency on >> package "winfsp-fuse". Then later when/if another FUSE implementation >> becomes available, "somebody" could replace the "fuse" package with >> whatever is required to get alternatives support for the variants. > > > Does setup.exe already have a provision in the GUI to ask the user > which one they want to chose if two or more packages are able to > provide the (empty) fuse package? > >> I'm wondering if "fuse-xxxx" is a better name template than "xxxx-fuse" in >> order to keep the variants near each other in setup.exe's displays. > > > good point. > > > Herbert Stocker