Re: package, package2, package3 naming-with-version exploit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/28/2013 12:47 PM, Toshio Kuratomi wrote:
> One disclaimer to start off --
> 
> We're on a big tangent here.  If I understood the original poster
> correctly, he'd concerned about what we name parallel installable
> versions of packages rather than whether we should have parallel
> installable packages at all.
> 
> That said, there's a lot to say about parallel installable packages
> so I'll jump in here.
> 
> On Thu, Mar 28, 2013 at 08:31:22AM -0400, Stephen Gallagher wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 03/28/2013 08:30 AM, Jan Zelený wrote:
>>> On 28. 3. 2013 at 12:59:44, Vít Ondruch wrote:
>>>> Dne 28.3.2013 12:09, Florian Festi napsal(a):
>>>>> This is done to make life easier for package maintainers.
>>>> 
>>>> Sorry, you definitely not speak for me! This are just
>>>> excuses. And I asked already several times to have some way
>>>> to reliable support multiple version of packages without
>>>> mangling their names.
>>> 
>>> Víťo, I certainly understand your frustration, as it comes
>>> from talking about this topic over and over again. However
>>> Ruby community is a *very* special case in this regard and I'd
>>> like to treat it as such.
>>> 
>>> If you want, we can start a discussion here. But if we do,
>>> let's keep the discussion strictly constructive and just about 
>>> *technical* problems. Let's not take this to design level of 
>>> things, as Ruby and Fedora are two completely different worlds
>>> that will never be fully compatible by design. Therefore the
>>> final solution (if there is any) has to be some sort of
>>> compromise.
>>> 
>> 
>> It's not just Ruby that has these issues, though. To take a
>> python example: Django. Most Django packages are built against a
>> specific minor version of Django, and the Django upstream
>> regularly breaks backwards compatibility with those minor
>> releases.
>> 
>> It ends up requiring Fedora to carry multiple copies of
>> python-django in the repo, usually versioning the older ones (so
>> in the current situation, we have python-django and
>> python-django14, with python-django referring to Django 1.5)
> 
> Note:  Is this a hypothetical?  I'm unable to find a
> python-django14 (or other versioned python-django) package build in
> koji.

Sorry, I forgot to reply to this. This was discussed on the thread
http://lists.fedoraproject.org/pipermail/devel/2013-February/179185.html
a while ago. The general sense was that we would function as above. I
then promptly forgot that the package review hadn't yet been finished
for python-django14.

I'm about to approve that review, unless this is being deemed
unacceptable by FPC (though it's not really in the guidelines).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFcG3wACgkQeiVVYja6o6NaxgCeKBxLAz3eNs8Tr8P8icxzoLiU
Z78AniyWtA4AtjtZlm9BO+7qqmJXVBzI
=5Rxw
-----END PGP SIGNATURE-----
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux