2008/7/14 Charlie Savage <[EMAIL PROTECTED]>: > > > Trans wrote: >> >> On Jul 14, 12:48 pm, Charlie Savage <[EMAIL PROTECTED]> wrote: >>> >>> Trans wrote: >>> >>>> On Jul 14, 12:34 pm, Charlie Savage <[EMAIL PROTECTED]> wrote: >>>>>> >>>>>> True as well. But I wouldn't say undoable. We can *responsibly* >>>>>> migrate. Or we can take a simpler solution and just wrap everything in >>>>>> LibXML module. Then in libxml.rb: >>>>>> include LibXML >>>>> >>>>> Ok - I can agree with that. Done. >>>>>> >>>>>> I leave it up to you all to decide what is best. All I ask is that the >>>>>> lib directory at least be called 'libxml'. >>>>> >>>>> Done. >>>>> With those changes, I'm going to cut a new 0.7.1 release unless there >>>>> are objections. >>>> >>>> Cool. But give me a few hours to check it out, okay? >>> >>> No problem. Just updating the RDocs at the moment. The namespace >>> change is checked in. >> >> Okay. I just did a little clean up. You'll notice I added an admin/ >> directory; this works well for separating administrative material. And >> I updated the Rakefile -- The gem's require_path needed ext/libxml >> added to it; and I made packages get stored in admin/pkg/ instead of >> pkg/. > > Sounds great. > > One question though - do we really want the pkg directory to be checked into > SVN? > > The issue is that rake clobber removes it, so then SVN gets confused when > the packages are rebuilt and the directory is recreated. If we do want it > in SVN, then rake clobber is going to have to be changed (which would mean > changing the rake packaging tasks assumedly).
Nope. we should add it to svn ignore property. T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel