Re: [Pkg-octave-devel] svn buildup
On Thu, Nov 29, 2007 at 10:18:45AM +0100, Rafael Laboissiere wrote:
> * Ólafur Jens Sigurðsson <ojsbug@gmail.com> [2007-11-28 23:58]:
>
> > On Wed, Nov 28, 2007 at 05:54:20PM -0500, John W. Eaton wrote:
> > > Why the specific version number? I think that may confuse people by
> > > leading them to believe that it is only intended for a specific
> > > version of Octave or that it is just a specific version of the Octave
> > > Forge packages. Maybe it would be better to just use the name
> > > octave-forge-pkgs?
> >
> > An even better suggestion, thanks John.
>
> Yes, it is.
>
> > As for this subdirectory idea, will that work for the guidelines from
> > http://pkg-octave.alioth.debian.org/DOG-Guidelines.html ???
> >
> > There it says that trunks and tags should be of the form
> > svn://svn.debian.org/svn/pkg-octave/<package>/tags/<version>/
> > but with the subdirs then it will be
> > svn://svn.debian.org/svn/pkg-octave/octave-forge-pkgs/<package>/tags/<version>/
> > right?
>
> Go ahead with the sub-directory implementation and I will adjust the
> Guidelines document later. Guidelines or Policies should follow the common
> practices, not the other way around.
Excellent, wasn't sure how you guys felt about this :-)
About the guideline then it says to create the directories manually
and copy them through the filesystem with cp and I did this for one
package and then when I issued svn add
octave-forge-pkgs/octave-statistics/trunk I got
svn: 'octave-forge-pkgs/octave-statistics' is not a working copy
svn: Can't open file
'octave-forge-pkgs/octave-statistics/.svn/entries': No such file or
directory
>From the good book (http://svnbook.red-bean.com/) then it shows an
example of initially importing a new tree into svn and they use
svn import mytree file:///path/to/code
should that not be used instead of the mkdir and cp command?
If not, then is a simple mkdir octave-statistics/.svn the right way to
solve the above issue? (I somehow doubt it will solve it at all :-) ).
Oli
Reply to: