On 2 August 2017 at 09:34, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
On Wed, Aug 02, 2017 at 09:23:05AM -0400, Stephen John Smoogen wrote:
> The issue I am seeing with this is that people who want to keep existing
> scripts are also wanting to keep existing package mechanism. If I say yum
> install httpd I am expecting to get the RPMs and setup I have for N years.
> I am not expecting to get a profile and modular set of tools decided by
> someone else who came up with a name httpd which matches a different case
> need. The same with WordPress or some other toolkit.
>
> If the module WordPress pulls in maria-db and my site has been using
> PostgreSQL, I am not just going to be confused.. I am going to be angry
> because my other scripts to seed the database aren't working. The quick
Good examples, thanks.
Do you think that this problem is as bad if we overload / replace /
enhance comps groups and the @ syntax? Or do we need to find a
different character? (Uh, I guess % is sitting out there....)
Again, if my scripts are using the @ symbol, I am expecting that I am going to get the @ syntax. As can be seen when the comps groups get broken in a main release, there are people who rely on it for deploying the system and expect that certain choices are 'made'. I would go with either a new symbol or keyword.
This will also help that people will also expect that the commands
dnf list, dnf remove, dnf <> will give the same data as dnf install does.
dnf list wordpress gives me
[root@f26 ~]# dnf list wordpress
Last metadata expiration check: 0:39:22 ago on 2017-08-02T09:07:22 EDT.
Available Packages
wordpress.noarch 4.8-1.fc26 fedora
If I do an 'dnf install wordpress' I expect to get that. Even if there is a wordpress group. I don't see that. I need a different syntax to see groups.
Available Modules
wordpress
section.. my script will now be confused. and I will definitely confused if I get a wordpress module of a different version than what the dnf list gave me.
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Stephen J Smoogen.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
