unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Function to find symlink target
Date: Sun, 05 Jun 2022 07:40:30 +0200	[thread overview]
Message-ID: <87o7z78y7l.fsf@dataswamp.org> (raw)
In-Reply-To: YphHacarJj7NvieB@protected.localdomain

Jean Louis wrote:

> Main use for symlinks on a GNU system is in libraries'
> directories:
>
>   lrwxrwxrwx   1    11 May 16  2020 aspell -> aspell-0.60

This is so you can just refer to - here - aspell and it will
lead you to a specific version, or just the version that is
currently installed.

>   lrwxrwxrwx 1   22 Mar 25  2021 libauthcustom.so -> libauthcustom.so.0.0.0
>   lrwxrwxrwx 1   22 Mar 25  2021 libauthcustom.so.0 -> libauthcustom.so.0.0.0

It has to do with versions as well:

  The symbol versioning is a GNU extension to library
  versioning [that] allows a single externally-versioned
  library (e.g. libc.so.6) to provide multiple incompatible
  implementations of the same symbol (before symbol
  versioning, you had to update the external version of the
  library every time you introduced incompatible interface;
  but with symbol versioning you don't). [1]

> Here are more practical example on finding files easier in
> file system by using symlinks for tagging

I have tagging with my e-mail, you can send a mail to
incal+even@dataswamp.org even ...

Not sure what tagging you refer to tho? Maybe symbolic (or
soft) links are pretty useless, is the disappointing truth?

[1] https://stackoverflow.com/a/20443988

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-06-05  5:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 20:55 Function to find symlink target Jean Louis
2022-05-18 23:00 ` Emanuel Berg
2022-05-22 13:52   ` Jean Louis
2022-05-22 18:02     ` Emanuel Berg
2022-05-23  9:05       ` Jean Louis
2022-05-23 20:46         ` Emanuel Berg
2022-05-24  0:59           ` Emanuel Berg
2022-05-24  1:09             ` Michael Heerdegen
2022-05-24  2:14               ` Emanuel Berg
2022-05-24  2:27                 ` Michael Heerdegen
2022-05-24  8:04                   ` Emanuel Berg
2022-05-24  8:52                     ` Michael Heerdegen
2022-05-25  5:54                       ` Michael Heerdegen
2022-05-27  2:25                         ` Jean Louis
2022-05-27  3:31                           ` Michael Heerdegen
2022-05-27  8:00                             ` Jean Louis
2022-05-27 14:47                           ` Emanuel Berg
2022-05-28  6:43                             ` Jean Louis
2022-05-28 15:29                               ` Emanuel Berg
2022-05-28 15:43                                 ` Emanuel Berg
2022-05-28 16:08                                   ` Eli Zaretskii
2022-05-28 16:46                                     ` Emanuel Berg
2022-05-28 16:55                                       ` Eli Zaretskii
2022-05-28 17:05                                         ` Emanuel Berg
2022-05-31  6:27                                 ` Jean Louis
2022-05-31 12:24                                   ` Emanuel Berg
2022-05-31  6:31                                 ` Jean Louis
2022-05-31 12:16                                   ` Emanuel Berg
2022-06-01  7:43                                     ` Jean Louis
2022-06-02  0:40                                       ` Emanuel Berg
2022-06-02  5:15                                         ` Jean Louis
2022-06-05  5:40                                           ` Emanuel Berg [this message]
2022-05-25  5:05                 ` Jean Louis
2022-05-25 22:33                   ` Emanuel Berg
2022-05-29  2:01                     ` Emanuel Berg
2022-05-19 23:14 ` Nick Dokos
2022-05-20  0:42   ` Emanuel Berg
2022-05-23  8:17   ` Jean Louis
2022-05-23 22:49     ` Michael Heerdegen
2022-05-23 22:57       ` Emanuel Berg
2022-05-24  0:59         ` Michael Heerdegen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7z78y7l.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).