Packages have "proxy" word.

[مصعب الزعبي]

Proxies not banned.

Date: Fri, 1 Nov 2013 00:20:35 +0100
Subject: Re: Packages have "proxy" word.
From: mkkp4x4 at gmail.com
To: devel at lists.fedoraproject.org

Hi,

Renaming packages it is not user friendly thing because of few reasons:
- there's some documentation/blog posts etc that use these names
- this will break installation scripts
- poeple who use these packages are familiar with these names

What if your country also ban "proxies" word?


2013/11/1 مصعب الزعبي <moceap at hotmail.com>




بسم الله الرّحمن الرّحيم

Hi,

The result of updating Fedora by yum is fail !!

When any package have "proxy" word marked to (install or update) , error message will appear with http 403 error forbidden.


In my country Syria (maybe others) all URLs have "proxy" word are forbidden and couldn't open by default way.

In Fedora there are two common packages and have many updates:

libproxy - sssd-proxy .


Can to rename to :

libproxies - sssd-proxies

Or something else.

Then do new rule to write "proxies" instead of proxy, at Fedora packaging guidlines.



Regards



-=-=-=-=-=-
Mosaab Alzoubi
Senior of Linux Arab Community http://linuxac.org
Member of Ojuba Project http://ojuba.org

Member of Arab Eyes project http://arabeyes.org
Maintainer of Almasa project
http://linux.softpedia.com/progMoreBy/Publisher-Almasa-47122.html

Maintainer of Arabic Translations in : Wine - VLC - KDE .... etc
Also member of Fedora Arabic translations team
 		 	   		  

--

devel mailing list

devel at lists.fedoraproject.org

https://admin.fedoraproject.org/mailman/listinfo/devel

Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


-- 
Best regards,

Michal

http://eventhorizon.pl/



-- 
devel mailing list
devel at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20131101/1ba4f76e/attachment.html>