All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-core] warning: symlink-is-self-recursive
Date: Tue, 22 Apr 2008 11:36:53 +0200	[thread overview]
Message-ID: <480DB1B5.10700@domain.hid> (raw)
In-Reply-To: <480A4F7F.4000909@domain.hid>

Hi,

Roland Stigge wrote:
> =========================================================================
> W: libxenomai-dev: symlink-is-self-recursive
> usr/include/xenomai/asm-generic/xenomai .
> N:
> N:   The symbolic link is recursive to a higher directory of the symlink
> N:   itself. This means, that you can infinitely chdir with this symlink.
> N:   This is usually not okay, but sometimes wanted behaviour.
> N:
> W: libxenomai-dev: symlink-is-self-recursive
> usr/include/xenomai/asm-sim/asm .
> W: libxenomai-dev: symlink-is-self-recursive
> usr/include/xenomai/asm-sim/xenomai .
> W: libxenomai-dev: symlink-is-self-recursive
> usr/include/xenomai/asm-x86/xenomai .
> W: libxenomai-dev: symlink-is-self-recursive usr/include/xenomai/xenomai .
> =========================================================================
> 
> I.e. installing Xenomai created those recursive links which might be
> there for source compatibility reasons. Can they be removed at some
> point or should I accept the above issue as intended for the future?

No comment from anyone? Maybe I should detect the necessity for those
links by removing and seeing if anyone complains? ;-)

bye,
  Roland


  reply	other threads:[~2008-04-22  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 20:01 [Xenomai-core] Debian lintian warning: symlink-is-self-recursive Roland Stigge
2008-04-22  9:36 ` Roland Stigge [this message]
2008-04-22  9:49   ` [Xenomai-core] " Philippe Gerum
2008-04-22 22:13     ` Gilles Chanteperdrix

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=480DB1B5.10700@domain.hid \
    --to=stigge@domain.hid \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.