From: Ralph Sennhauser <sera@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Clarifications on dosym behaviour
Date: Fri, 27 Jan 2012 22:59:19 +0100 [thread overview]
Message-ID: <20120127225919.44d0f2de@sera-17.lan> (raw)
In-Reply-To: <20258.63902.6759.139613@a1i15.kph.uni-mainz.de>
On Fri, 27 Jan 2012 20:23:10 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> 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.
>
Thanks for the clarifications.
Cheers
prev parent reply other threads:[~2012-01-27 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 18:05 [gentoo-pms] dolib description misses DESTTREE Ulrich Mueller
2012-01-27 16:29 ` [gentoo-pms] Clarifications on dosym behaviour Ralph Sennhauser
2012-01-27 19:23 ` Ulrich Mueller
2012-01-27 21:59 ` Ralph Sennhauser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120127225919.44d0f2de@sera-17.lan \
--to=sera@gentoo.org \
--cc=gentoo-pms@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox