Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
--- Comment #5 from Toshio Ernie Kuratomi <a.badger(a)gmail.com> 2010-11-30 12:18:37
Hey Steven, going to what MochiKit does is probably a step backwards from what
is posted in my last package. I was doing this package while working on the
MochiKit did and made improvements from there.
This basically stalled because I wanted to get the Packaging Guidelines for
Here's the draft documentation:
If you'd like to work on the draft a lot of people would be very pleased! The
things that came up when the FPC discussed it were:
probably go in different directories than the browser-libraries, etc.
2) Over time I've come to believe that a static linking model is more
example, an application needing jquery would use the code in this package when
it builds but it would be free to copy the jquery from this package into
itself. When this jquery package updates, the web application would need to be
ported to the new version of jquery at that time. Provides and Requires
similar to that used for static linking would be used to track what libraries
at what versions are being statically linked.
3) We need to anticipate handling of multiple versions of a library. For many
years, we're going to find that different applications work with different
a time will it become normal for upstreams to port to newer versions of the
their server-language's libraries.
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.