Open twojstaryzdomu opened 3 years ago
@twojstaryzdomu don't waste your time with pricks like that. I have blocked them now.
@MaxKellermann, there was no needed to block him. Albeit arrogantly, he did make a point about symbolic links being a possible work around to the music_directory
restriction. I opened #1535 to request resolution of symlinked paths to plugin-based sources.
Alternative proposal to enable multiple music sources non-interactively.
Feature request
MPD appears to support a single music_directory path. Enabling additional directories via multiple music_directory calls would be a convenient feature.
A single music_directory works only on the assumption the user keeps their music in a single location. Some users may have their music on multiple drives, including removable ones, which they may be connecting at any time when MPD is already running.
Failure to find the directory at start time should not be taken as assumption the path won't ever become available during the lifetime of the MPD process.
The simplest use case for missing paths at start time is for use with removable media, which sit in mountpoints under
/media/<username>
(controlled by udisks2), which may not be present if no removable media is inserted. It would be up to the user to scan the media, so polling for changes (with auto_update) need not apply to the directory.To clarify how it would work: a user could set their local music_directory and add a second music_directory clause pointing to
/media/<username>
. The former would work with auto_update, whilst the latter path would be scanned for files whenever the user specifically requests MPD to do so.