incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter" <brett.por...@gmail.com>
Subject Re: [IVY] setup of infrastructure
Date Wed, 01 Nov 2006 21:17:09 GMT
Usually, a dumpfile is used rather than a zipped up repository, I think.

I would suggest locating an svn admin who can work with you to do a
test now - so you'd dump the repository without locking it out, load
it up into the test repository, check it works, so that you know what
to do and minimise downtime of your commit access when you are ready
to do the real thing.

I'm not an svn admin either, though - so best to get in touch with
them and see how they usually do it :)

Cheers,
Brett

On 02/11/06, Upayavira <uv@odoko.co.uk> wrote:
> Xavier Hanin wrote:
> > On 11/1/06, Upayavira <uv@odoko.co.uk> wrote:
> >>
> >> Xavier Hanin wrote:
> >> > On 11/1/06, Brett Porter <brett.porter@gmail.com> wrote:
> >> >>
> >> >> On 31/10/06, Xavier Hanin <xavier.hanin@gmail.com> wrote:
> >> >> > > Does Ivy want to import history, or just the latest code?
> >> >> >
> >> >> >
> >> >> > An history import would be nice, but isn't there a problem with
> >> legal
> >> >> > issues, since old code was not under Apache License? And maybe
the
> >> >> easier is
> >> >> > just to import latest code (well, I should release a new version
> >> next
> >> >> week -
> >> >> > maybe the last pre apache version, so it may be a good time to
> >> import
> >> >> just
> >> >> > after the release). What do other think?
> >> >>
> >> >> If it were me, I'd rather import the history than having to maintain
> >> >> it myself. There are no legal issues (BSD is compatible with the
> >> >> Apache License).
> >> >
> >> >
> >> > Thanks for your advice Brett. I'll go with history import if it's not
> >> too
> >> > complex to import into apache infrastructure. Can someone tell me what
> >> you
> >> > expect from our svn repository to do the import?
> >>
> >> If you can block all commit access to the repository, then a simple zip
> >> should do the job, If I understand correctly.
> >
> >
> > I can block access to the repository. So the only thing is to zip the
> > directory on my svn server containing the db directory, is that it? This
> > means that the hook directory will be part of the zip, I currently have a
> > hook for sending mail on commit, but I think there's already something like
> > this on apache usual svn install, no? So maybe the db directory is enough?
> > We use a filesystem based svn repository, is that ok? It's a lot of
> > question
> > I'm sorry, but I'm not familiar with ASF infrastructure.
>
> No, the hooks directory won't be needed. However, I'm not as
> knowledgeable as you might think, and would suggest you just zip up the
> lot, including hooks directory, just to be safe, unless someone else
> more knowledgeable tells you otherwise.
>
> Regards, Upayavira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message