On Mon, 10 Oct 2011, Luis A. Bastiao Silva wrote: > 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)?
well -- ideally all external dependencies should be separately packaged and yes -- listed in Depends (or Recommends or Suggests depending on how critical they are) -- and your source distribution should include only source code for your project. So whoever approaches dicoogle first, for packaging, would need to do that -- go through the list of .jar's you ship and see which ones are available on Debian system, which are not? which might be incompatible version-wise, and which might be conflicting in licensing... etc Do you have somewhere such a description? altogether -- I don't see anyone yet expressing desire to jump onto packaging (yet), nor there is an RFP (request for packaging) bugreport; so you might start from there: on Debian system do reportbug wnpp then specify 'RFP' and fill out the form. That might bring additional interest alternatively -- someone from your company might like to get familiar with Debian packaging, and start working on the package while consulting the mailing list whenever got stuck/ran into the problem. Cheers, -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
