On 11/05/2013 06:58 PM, Toshio Kuratomi wrote:
On Tue, Nov 05, 2013 at 12:58:30PM +0100, Marcela Mašláňová wrote:
> Yeah, we were discussing some vendor prefix to make a distinction
> between collections with same content and same name. We were thinking
> about user or vendor not general scl.
> We are still discussing the best way, because currently redefinition
> of /opt/vendor is not nice. There is needed a fix in scl-utils:
the last reply to that bug seems to say that prefixing the package names
with the vendor is the way to go.
This way has one another benefit that I haven't seen mentioned yet.
Since files that have to be located outside of SCL root (like systemd
unit files, logrotate files, ...) cannot conflict with files from core
system, we usually need to prefix them with SCL name. So we end for
example with /etc/logrotate.d/mariadb55-mariadb.
However, imagine we wanted to install two collections with the same name
(mariadb55) and different vendor (fedora vs. skysql) -- then the files
outside SCL root would conflict and we wouldn't be able to install them.
Including vendor into collection name will solve this, even though the
service names get even more ugly:
"systemctl status fedora-mariadb55-mariadb"