nodejs-packaging [was: Handling Multiple Version Scenarios]

[T.C. Hollingsworth]

On Tue, Jun 4, 2013 at 6:56 PM, T.C. Hollingsworth
<tchollingsworth at gmail.com> wrote:
> The "inherits" module has a new breaking version out, and some modules
> are now using both versions.  Jamie and I ran into something like this
> with uglify-js, and we just hacked around it for then, but doing that
> for this situation would probably take longer than just finding a nice
> way to make this easier generally, so lets do that.  ;-)

This is now done as part of the Great nodejs-packaging Split we've
discussed previously.  The review is here:
https://bugzilla.redhat.com/show_bug.cgi?id=974005

I went with the simple text file approach; it makes things simpler for
package maintainers and if it grows to be too unwieldy we'll need to
drastically reconsider our approach anyway...

No action is required of maintainers at this time.  I believe I
already have ACLs on all the packages that will be affected by the
nodejs-inherits split once that takes place, but if not I'll bother
maintainers about that when the time comes.  (All that will be
required is a simple rebuild.)

Everyone who previously had git access to the nodejs SRPM should now
have git access to nodejs-packaging upstream git as well.  You can
find it in fedorahosted git:
http://git.fedorahosted.org/cgit/nodejs-packaging.git
(or `git clone git.fedorahosted.org:nodejs-packaging.git`)

There's also a clone at github if you want to subscribe to commits or
take advantage of other github features:
https://github.com/tchollingsworth/nodejs-packaging

I'll accept pull requests on github if that makes it easier for people
(not to mention it doesn't let me turn them off ;-), but otherwise
Issues and such are turned off, nor did I bother with a Trac instance
for this; it all seems like overkill.  Please file bugs against the
nodejs-packaging component in bugzilla when it exists.

-T.C.