Looks good. Thanks.

On Thu, Jan 28, 2010 at 10:07 PM, marekj <[email protected]> wrote:

> What an adventure.
> So the first thing I wanted to to do was to move the current rdoc/* to
> rdoc/1.6.2/
> and then post the new 1.6.5 docs to rdoc/1.6.5/
>
> Anyway
> Here are some problems I didn't think about.
> - Rubyforge does not provide the interactive ssh so you can't ssh into
> the machine
> - you can't execute remote commands (again, restricted access)
> - you can scp or sftp (perhaps rsync as well) but none of those allow
> me to 'rm' or 'mv' files or dirs
>
> task 'copy current rdoc files to it's own subdir' do
>  I pulled remote files to local machine
>  and scp it back to rdoc/1.6.2/
> end
>
> task: 'remove leftover old files'
> I was able to sftp into the account and I was able to remove some
> stuff with rm and rmdir
> but I get 'permission denied' for classes and files directories and files.
>
> This is the first time I've worked with a restricted acces ssh and I
> am curious if there is an easier way to manage remote files
> I guess using rsync with --delete option may work
> anybody has any ideas how I can remove the old files?
>
> posted new docs
> http://wtr.rubyforge.org/rdoc/1.6.5/
>
> however they come from the my rdocfix fork. I'll keep working on
> removing unittests from gem packages in hopes of next minor release.
>
>
>
>
>
>
>
> marekj
>
> Watirloo: Semantic Page Objects in UseCases
> http://github.com/marekj/watirloo/
> Support Watir Project http://pledgie.com/campaigns/2982
>
>
>
> On Wed, Jan 13, 2010 at 9:41 AM, Bret Pettichord <[email protected]>
> wrote:
> > Marek know has rights to upload to our rubyforge website. Here are my
> stale
> > notes documenting the old procedure on how to update the rdocs in case
> this
> > is helpful:
> > http://github.com/bret/watir/blob/master/watir/watir_release.txt
> >
> > On Wed, Jan 13, 2010 at 6:12 AM, Željko Filipin
> > <[email protected]> wrote:
> >>
> >> On Wed, Jan 13, 2010 at 1:59 AM, marekj <[email protected]> wrote:
> >> > I like how rspec guys keep their rdocs
> http://rspec.rubyforge.org/rspec/
> >> > I suggest we do the same for http://wtr.rubyforge.org/rdoc
> >>
> >> +1
> >>
> >> > I spoke with Bret, he's going go give me rubyforge access
> >>
> >> If you need any help with that just let me know.
> >>
> >> > and if you like the rdoc currently generated by hanna template.
> >>
> >> World is small, I know Mislav, creator of Hanna (he is from Zagreb).
> >>
> >> > http://rubytester.com/test/watir/rdoc/
> >>
> >> This looks great! :)
> >>
> >> Željko
> >>
> >> _______________________________________________
> >> Wtr-development mailing list
> >> [email protected]
> >> http://rubyforge.org/mailman/listinfo/wtr-development
> >
> >
> >
> > --
> > Bret Pettichord
> > Lead Developer, Watir, www.watir.com
> >
> > Blog, www.io.com/~wazmo/blog <http://www.io.com/%7Ewazmo/blog>
> > Twitter, www.twitter.com/bpettichord
> >
> >
> > _______________________________________________
> > Wtr-development mailing list
> > [email protected]
> > http://rubyforge.org/mailman/listinfo/wtr-development
> >
> _______________________________________________
> Wtr-development mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/wtr-development
>



-- 
Bret Pettichord
Lead Developer, Watir, www.watir.com

Blog, www.io.com/~wazmo/blog
Twitter, www.twitter.com/bpettichord
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to