Hi, I find the docs a little confusing with regards to how a packager should name a service or instance.
If we packager, for example, postfix, which provides smtp service, then the docs seem to suggest that the service name should be 'network/smtp', and then we should have an instance, named, for example 'postfix2210', possible including a stock symbol in the instance name. Am I right so far? My problem with the documentation comes when packaging services that are not already on the system, lets take mysql as an example. I have seen two manifests for mysql on the web, one used by blastwave, the other on the bigadmin site. One names the service network/mysql, the other says application/mysql. It is possible that our customers also use blastwave or some other packaging systems, we do not want to overwrite their entries in the database, but still we want to make sense. We're inclined to go with application/mysql and define an instance with or stock symbol in the name, our package will not overwrite any other package and it is possible that a number of mysql be installed on the system at any one time. The documentation suggests though that the service name should contain the stock symbol, rather than the instance name. We're trying to do thir "right" so advice is appreciated. Thanks, Peter
