Hi again, On Mon, Oct 10, 2011 at 10:29 PM, Yaroslav Halchenko <[email protected]>wrote:
> ;-) It is not necessary for Debian packaging effort per se as long as > you distribute the source tarballs (which you do). > > Fine. We will see if we can come up with a public repository. We've several restrictions due to the faculty where the project is hosted. > It is just me -- I thought to look into dicoogle, how active it is in > terms of development, what is the internal organization of the project > (versus "source distribution" which already brought concerns regarding > packaging due to bulk of .jars distributed along and requiring clean > look on them), who is developing it most (committers), etc. > > Our development is committers, although we accept external patches. Regard the libraries that we are depending, you're right. We've a lot of external dependences. We're thinking to migrate to maven to outsource this responsibility but it is a costly operation right now. What is the way to distribute it in Debian? Just Dicoogle.jar without any external dependence? Is it only allows debian dependences (i.e.debian/control -> Depends)? > That is why I spent some time online trying to find public VCS but > failed. > > On Mon, 10 Oct 2011, Luis A. Bastiao Silva wrote: > > on pretty much unrelated to packaging topic: I think I haven't > > found any public VCS for dicoogle -- I wonder if there is any > publicly > > available? > > > Thanks for quickly reply. So can you clarify to me what the goal of > the > > topic please? > > Right now our repository is closed. I can request for the project > manager > > to put them available online. (Or at least give a push times to > times). Is > > it really necessary? > -- > =------------------------------------------------------------------= > Keep in touch www.onerussian.com > Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic > -- Luís A. Bastião Silva Skype: koplabs http://www.bastiao.org
