Re: How to start if upstream source contains pom.xml

[Andreas Tille <andreas@an3as.eu>]

Hi Emmanuel,

On Thu, Jul 17, 2014 at 10:14:38AM +0200, Emmanuel Bourg wrote:
> > What would be the correct answer at this point of the process.
> 
> The right answer here is: s/.*/debian/
> But mh_make shouldn't ask as there is not ambiguity here, I'll see if I
> can improve that. If you install the libcommons-fileupload-java package
> before running mh_make the dependency will be matched automatically.

I can confirm that *this* issue is solved then but I needed to answer
some other questions.  However, in the end I did not got any control,
changelog or control file as the doc[1] is promissing:

  That's it. Now I have a debian folder, and it contains changelog,
  control, rules, copyright and a few other files.

Is this because of the missing edpendencies or is anything else wrong
here?
 
> > How do I get this "not yet packaged dependency list"?
> 
> If you look into the pom.xml file you'll see the list of dependencies.
> Then you can use 'apt-file find' with the artifactId and see if a
> package contains the dependency expected.
> 
> For example the pom declares this dependency:
> 
>     <dependency>
>       <groupId>org.apache.jena</groupId>
>       <artifactId>apache-jena-libs</artifactId>
>       <type>pom</type>
>       <version>2.11.0</version>
>     </dependency>
> 
> You look for the dependency with:
> 
>     apt-file find apache-jena-libs
> 
> No result is returned, this is a missing dependency.

OK.
 
> > Just some backround information:  I'll hold a packaging workshop at
> > 21.+22.7. and the participants have choosen this package as their final
> > target.  So I could do some demonstration perhaps on the preconditions.
> 
> Considering the amount of missing dependencies you may start with imeji
> and then pick an easy to package dependency. But you won't be able to
> package everything in only one session. Looking at the list sanselan is
> a good candidate (simple structure, all dependencies in Debian).

Thanks for the hint - this sounds quite reasonable.
 
> Alternatively, if you just want to create a .deb package but not
> distribute is through the Debian archive, using jdeb would be an easier
> alternative:

Its a goal of the audience to finally create an official package of
this and other interesting software.

Kind regards and thanks for your helpful hints

      Andreas.

[1] https://wiki.debian.org/Java/MavenDebianHelper

-- 
http://fam-tille.de