On 11/1/06, Upayavira <[EMAIL PROTECTED]> wrote:
Xavier Hanin wrote: > On 11/1/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> >> On 31/10/06, Xavier Hanin <[EMAIL PROTECTED]> 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. - Xavier Regards, Upayavira
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
