I use this package for a long long time mow. Without problem. I have the conflict nit without a reason insert. I test all my packages self. But you can test it by yourself. Not only build. Test it live!
I think you mean that they both want to mount their website on localhost /git/ in their apache config.
If I am understanding that correctly, that isnt a conflict that rpms Conflicts should be used to resolve. That is a user config. And gitea doesnt even Suggest: apache , as gitea doesnt need apache.
I can't agree with, first gitweb install a apache instance wide alias, which is by default a very immature way of doing it (except in container). so if an admin disable gitweb.conf in /etc/apache2/conf.d/gitweb.conf and as it defined in a vhost git.domain.tld he can also have a gitea powered vhosts with its own alias and other git engine.
So technically in the actual state either gitea or gitweb should have a /git/ alias defined, but both should be installable by users.
How many times must I this explain again.
Gitea and gitweb is similar.
When use gitea you have no need for gitweb. And I will the alias to git.
If you not believe me, than test it. Install both packages.
Don't get it personal, we try to explain you, that perhaps your vision is somewhat limited.
gitweb and gitea are similar, but you have no idea how and what is needed to serve my customer needs. Which is a kind of restriction that is not real (to be formulate in terms of packaging : the content of each package doesn't conflict on the filesystem, nor commands).
You can't say that I have to drop some of customer (those using gitweb) because I've new customer that want to use gitea. It would be super cool to drop your conflict line, as it can help other to use your(our) package.
Both package work perfectly, as I previously said, I've both of them running on two distinct vhosts, the patch I've done is comment out all stuf in etc/apache2/conf.d/gitweb.conf
You should try, you could be surprised :-)
How does gitea conflict with git-web ? I dont see any overlapping resources needing use of Conflict.
I use this package for a long long time mow. Without problem. I have the conflict nit without a reason insert. I test all my packages self. But you can test it by yourself. Not only build. Test it live!
Both use alias git.
git-web is a rudimentary gui. When someone install gitea, he does no more need git-web. It makes no sense to install both.
And i want not change the alias to something else. And i think the maintainer from git-web also.
I am having difficulty understanding 'alias git'
I think you mean that they both want to mount their website on localhost
/git/in their apache config.If I am understanding that correctly, that isnt a conflict that rpms Conflicts should be used to resolve. That is a user config. And gitea doesnt even Suggest: apache , as gitea doesnt need apache.
No! When you install both gitea does not run!!!
I can't agree with, first gitweb install a apache instance wide alias, which is by default a very immature way of doing it (except in container). so if an admin disable gitweb.conf in /etc/apache2/conf.d/gitweb.conf and as it defined in a vhost git.domain.tld he can also have a gitea powered vhosts with its own alias and other git engine. So technically in the actual state either gitea or gitweb should have a /git/ alias defined, but both should be installable by users.
How many times must I this explain again. Gitea and gitweb is similar. When use gitea you have no need for gitweb. And I will the alias to git. If you not believe me, than test it. Install both packages.
Don't get it personal, we try to explain you, that perhaps your vision is somewhat limited.
gitweb and gitea are similar, but you have no idea how and what is needed to serve my customer needs. Which is a kind of restriction that is not real (to be formulate in terms of packaging : the content of each package doesn't conflict on the filesystem, nor commands). You can't say that I have to drop some of customer (those using gitweb) because I've new customer that want to use gitea. It would be super cool to drop your conflict line, as it can help other to use your(our) package.
Both package work perfectly, as I previously said, I've both of them running on two distinct vhosts, the patch I've done is comment out all stuf in etc/apache2/conf.d/gitweb.conf You should try, you could be surprised :-)