Closed lbraglia closed 9 years ago
What do you think about a variable NONPKGTARGETS := get-default help maker ...
? Than you could use NONPKGTARGETS += create
in your .makerrc
. This would be very flexible.
NONPKGTARGETS := get-default help maker
seems a great solution.
definitely better, thanks
Hi (sorry for long post)
before default PKG i could use something from my
makerrc
to create a package from scratch (mainly using devtools)that is currently defined as
which is fine to me because it creates a package from cli that is ready to be coded and pushed to github.
Now since default PKG has been introduced, it doesn't work anymore because
PKG/NAMESPACE
does not exists yet (that's just what the create target does). But that is a fine/safe check to do, and should definitely remain.Therefore now i'm using a little modified version of maker which add
create
to the allowed targets in absence ofPKG/NAMESPACE
I think adding an "official create" (or same, but different-named, target) would be badly addressed because the standard package setup is mainly a matter of tastes (eg one could use package.skeleton, devtools' create, Rcpp.package.skeleton, pkgKitten and so on... not to mention the optionals, eg roxygen, travis, git/svn support etc) but allowing the user him/herself to define a create target which is allowed to work in absence of
PKG/NAMESPACE
could be nice IMHOIn the case, i could be write something in recipes to document it
what do you think? @lgatto @sgibb