On Fri, Nov 08, 2013 at 03:57:12AM -0000, Adam Conrad wrote:
> 5) Please talk to upstream about that weird non-FHS legacy path. If
> they can live without it, we really don't want stuff like that setting
> a precedent for other people thinking it's hip and cool to litter all
> over standards and the filesystem.
Could we, for example, use cloud-init's user data vendor merging thing to
have a runcmd create the symlink only when it's needed, to keep it out
of the packaging? Just a thought.
On Fri, Nov 08, 2013 at 03:57:12AM -0000, Adam Conrad wrote:
> 5) Please talk to upstream about that weird non-FHS legacy path. If
> they can live without it, we really don't want stuff like that setting
> a precedent for other people thinking it's hip and cool to litter all
> over standards and the filesystem.
Could we, for example, use cloud-init's user data vendor merging thing to
have a runcmd create the symlink only when it's needed, to keep it out
of the packaging? Just a thought.
What is the use case for needing the symlink?