From: Jan Stary <hans@stare.cz>
To: "Måns Rullgård" <mans@mansr.com>
Cc: sox-users@lists.sourceforge.net
Subject: Re: symlinks
Date: Tue, 11 Aug 2020 19:25:50 +0200 [thread overview]
Message-ID: <20200811172550.GA55134@www.stare.cz> (raw)
In-Reply-To: <yw1xzh71tcfk.fsf@mansr.com>
> >> > How is using alsa/oss/sndio/whatever
> >> > related to creating symlinks (or not)?
> >> >
> >> > Why do we have both SYMLINKS and PLAYRECLINKS?
> >> > Why is this different for play/rec vs soxi (also below)?
> >> >
> >> > Naively, I would assume we want to create symlinks
> >> > for each of play, rec, soxi, or none of them.
> >>
> >> There is no point in creating play/rec symlinks
> >> when no audio devices are supported since they can't work then.
> >
> > The current build system seems to omit sunaudio and waveaudio
> > from the list above, but with the rationale you describe,
> > they should be there too, right? Or is this intended?
>
> Sorry, I missed that.
>
> > Anyway, the manpages still get symlinked even if play/rec don't,
> > e.g. when all the drivers ar explicitly disabled. Is that intended?
>
> I missed that too. The whole thing is a mess.
I don't think the complexity is worth it at all.
Why not just create a symlink for play, rec, and soxi,
and a symlink for the play.1 and rec.1 manpages, always?
In the worst case, we create a needless symlink.
(And than the user plugs a soundcard in and runs play,
which is no longer needless, as opposed to recompiling).
The alternative is this mess we have now.
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2020-08-11 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 14:12 symlinks Jan Stary
2020-08-11 14:25 ` symlinks Måns Rullgård
2020-08-11 15:30 ` symlinks Jan Stary
2020-08-11 15:44 ` symlinks Måns Rullgård
2020-08-11 17:25 ` Jan Stary [this message]
2020-08-11 17:27 ` symlinks Måns Rullgård
2020-08-12 7:08 ` symlinks Jan Stary
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200811172550.GA55134@www.stare.cz \
--to=sox-users@lists.sourceforge.net \
--cc=mans@mansr.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
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).