Skip to content
This repository has been archived by the owner on Sep 23, 2018. It is now read-only.

Release v0.7 #65

Open
landroni opened this issue Dec 17, 2012 · 6 comments
Open

Release v0.7 #65

landroni opened this issue Dec 17, 2012 · 6 comments
Milestone

Comments

@landroni
Copy link

Currently it is not possible to install 'tikzDevice' from CRAN.

http://cran.r-project.org/web/packages/tikzDevice/ :
"Package ‘tikzDevice’ was removed from the CRAN repository.

Formerly available versions can be obtained from the archive.

This package has been archived: the maintainer felt unable to provide an update fixing WARNINGs within reasonable amount of time."

install.packages( 'tikzDevice' )
Installing package(s) into ‘/usr/local/lib/R/site-library’
(as ‘lib’ is unspecified)
Warning in install.packages :
package ‘tikzDevice’ is not available (for R version 2.15.2)

Is this expected?

@Sharpie
Copy link
Owner

Sharpie commented Jan 5, 2013

Is this expected?

See the mailing list:

https://groups.google.com/d/topic/tikzdevice/73Hd2Eln3Qk/discussion

@Sharpie
Copy link
Owner

Sharpie commented Apr 20, 2013

Re-purposing to a general "get version 0.7 released" issue. Things that need to happen:

  • Close out issues targeted at the 0.7 milestone.
  • Sort out GitHub -> R-Forge bridge so pre-releases can be tested again.
  • Ensure NEWS.md -> R NEWS conversion still works.
  • QA Testing for OS X
  • QA Testing for Linux
  • QA Testing for Windows
  • QA Testing for Solaris

(more will be added as issues pop up)

@JanMarvin
Copy link

If you add the NAMESPACE file to the repo the devtools package should work.

#install.packages("devtools")
require("devtools")
install_github("RTikZDevice",username="Sharpie")

@Sharpie
Copy link
Owner

Sharpie commented Apr 21, 2013

NAMESPACE is dynamically generated by ROxygen along with a bunch of other stuff.

@fmitha
Copy link

fmitha commented Jun 8, 2013

Hi. I use RTikZDevice, and I'm a little concerned this very useful package may die. Is there anything that I (as someone who is software literate but not familar with the internals) can do to help with the 0.7 release? Specific recommendations/suggestions appreciated. Would issue 69 (fix failing tests) be something a user could help with?

@krlmlr
Copy link

krlmlr commented Jul 25, 2013

@Sharpie:

Sort out GitHub -> R-Forge bridge so pre-releases can be tested again.

What's wrong with it? I wanted to steal it :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants