At 12:33 PM +0200 4/28/00, Gabriele Bartolini wrote:
>> The ht://Dig project is only a repository for the latest beta version
>>at present but it would be really nice to see it become a central repository
At the moment, there is nothing in the SourceForge CVS tree. For us
to switch to using SourceForge for CVS, all developers would need to
sign up for SourceForge accounts. I'm not sure this is the right move
to make right now. (For example, we'd need to move a lot of
infrastructure like LXR and the snapshot script.) Also everyone would
need to check out the CVS tree again. With my modem connection,
that's not very pleasant.
So right now, I'm using the ht://Dig space on SourceForge merely as a
fancy mirror. The task and patch managers might be useful, but
otherwise it seems like there isn't a great reason to migrate
existing structure--I'd even prefer if the SourceForge project could
link to our existing bug database, etc. (I requested it, no answer. I
may have to write it myself.)
For the case at hand, I don't see a problem with Gabriele having an
independent project. There are already several projects that are
ht://Dig related, including ConfigDig and mifluz (lest you forget
Loic). There are also a few that use ht://Dig under a shell to index
and search like KDevelop and now Codebank.
I say it's up to Gabriele. I think it's fair enough for him to have
his own project--more exposure for him, and easier to keep things
separate (bugs, tasks, CVS trees).
>Probably before taking a decision, you should try it ... but I don't
>want to fill the mailing-list with a tar.gz file (I am gonna send it
>privately, ok?).
Actually you could upload it to SourceForge anyway--if you decide to
go as a module, it can be easily deleted.
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
