From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RqrOO-0006LF-OD for garchives@archives.gentoo.org; Fri, 27 Jan 2012 19:23:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 875EFE071C; Fri, 27 Jan 2012 19:23:12 +0000 (UTC) Received: from a1iwww1.kph.uni-mainz.de (a1iwww1.kph.uni-mainz.de [134.93.134.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 2A246E071C for ; Fri, 27 Jan 2012 19:23:11 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92]) by a1iwww1.kph.uni-mainz.de (8.14.4/8.13.4) with ESMTP id q0RJNAgR026999 for ; Fri, 27 Jan 2012 20:23:10 +0100 Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1]) by a1i15.kph.uni-mainz.de (8.14.5/8.14.2) with ESMTP id q0RJNAUI030965; Fri, 27 Jan 2012 20:23:10 +0100 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.5/8.14.5/Submit) id q0RJNAGc030964; Fri, 27 Jan 2012 20:23:10 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Package Manager Specification discussions X-BeenThere: gentoo-pms@gentoo.org X-BeenThere: gentoo-pms@lists.gentoo.org Reply-To: gentoo-pms@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20258.63902.6759.139613@a1i15.kph.uni-mainz.de> Date: Fri, 27 Jan 2012 20:23:10 +0100 To: gentoo-pms@lists.gentoo.org Subject: Re: [gentoo-pms] Clarifications on dosym behaviour In-Reply-To: <20120127172942.5b8b42fa@sera-17.lan> References: <20229.59009.340367.69931@a1i15.kph.uni-mainz.de> <20120127172942.5b8b42fa@sera-17.lan> X-Mailer: VM 8.2.0b under 23.4.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller X-Archives-Salt: 844b48bc-ec8e-4983-824a-8183728c9b68 X-Archives-Hash: a58d10e2e57617770aad4f1f2cb4261c >>>>> On Fri, 27 Jan 2012, Ralph Sennhauser wrote: > Just recently Portage started to emit "* QA Notice: dosym target > omits basename ..." for "dosym /path_to_file/file /some_other_path/" > The PMS says: > dosym: Creates a symbolic link named as for its second parameter, > pointing to the first. If the directory containing the new link does > not exist, creates it. Failure behaviour is EAPI dependent as per > section 12.3.3.1. > The part "Creates a symbolic link named as for its second parameter" > could qualify it for requiring a basename. Exactly. > As the behaviour of an implicit basename of the second parameter was > used for a long time I wonder if the PMS needs to be updated and > clarify the dosym behaviour or if this new QA warning can be seen as > a long overdue implementation of the intended behaviour. This has been discussed in bug 379899 and the conclusion was that PMS specifies the intended behaviour. At the moment a directory argument produces only a QA warning in Portage. I think the long-term plan is to turn it into an error though.