Hi,

I'm working on a packaging helper tool in the Debian-Java team. I'm looking to
reuse some modules from dh-make-perl. It's possible to depend on the
dh-make-perl package. But it might encourage more adoption by other teams if
the perl independent logic would be separated in a library of its own.

Currently I'm aware of the following packaging helpers:

jh_makepkg, maven-debian-helper, dh-make, dh-make-perl, dh-make-php,
dh-make-drupal, gem2deb, python-stdeb, haskell-devscripts, dh-lua

Regards, Thomas Koch
iQIcBAEBCAAGBQJRZElZAAoJEAf8SJEEK6Za+F8P/iccfcpgCuO8TtNBLvuKAFpZ
2vIKNNE0dPeJLMp9j9jF+8x4n97jvk9hP/fwbdfI0Jj5qSTDzOCawOKchGCUBG0k
lCZvkXVsDa/e/xYz3gPfBCSQ3op2wokWTuhjxtBrFG9U6DV/FMaSaiF7j3y15LMT
nbu2OFQs8RP0Su50Rqj6cqcTJMb0aT5bXyDN1xciJk4yaYAp6ViVN5F5pEJSXCjN
E3siKcgmCDJphlA61J+YjjlEazwtLiDQQpBrmorgpKSFy2zKBD4TgOKwmaV+G5l5
JXrR57HsNnTyvzgewc0uuTcCJdZvlUcTyLUM1UtDXvVZuKvqN6GTPS9j63SkiTgP
nvwAa0JwvJDR5ctzIuRS0qF/plF4Eg5Cc88HuAdIBId5Q27tcurLSQ6PakGfsLvA
GXcucEsr60HzGGeaJeZuSmKkv51FtmMbewj+eKQlLI1F48yj4b1MUaZ8vNuS8zB7
qhOo36CUCx8l60mPH9a91bdmvPpWt+67lRmQOxzeMZzRblDjtz1A1DJ+L3+vlmHv
ku+tt5nIRYAqrdkMS9ItGX7TbMrYPBEk9SJBNR8VrV12cyy72xv4WvYgakpFF/8k
pgL3RbX6j48Lq6D2Fo4q0UdjxCF3pxzTY2ThIjyA+ucaSv3M3a87Ds7t5oaUnh+s
o66aXroJmSuRNg9xDLIo
=bou6
-----END PGP SIGNATURE-----

Thomas Koch <thomas@koch.ro> writes:

Hi Thomas;

I'm not sure what precisely you're proposing (I'm also not one of the
team members working on dh-make-perl, so don't get too excited ;) ).

Are you suggesting splitting dh-make-perl into two packages? It seems
like one of them would be just a script, and a bit silly.  Or is your
request more about documenting and/or fixing library interfaces?

d

Thomas Koch <thomas@koch.ro> writes:

Hi Thomas;

I'm not sure what precisely you're proposing (I'm also not one of the
team members working on dh-make-perl, so don't get too excited ;) ).

Are you suggesting splitting dh-make-perl into two packages? It seems
like one of them would be just a script, and a bit silly.  Or is your
request more about documenting and/or fixing library interfaces?

d

model-dpkg-perl. (used by 'cme check dpkg'). You will get a dpkg lib which is
independant of perl. This lib can read, check, modify and write most files in
debian/ .

You could use this in a program that would:
- parse info from java stuff
- adapt it and load it in libconfig-model-dpkg-perl lib.

Then checking the info and writing package files would be handled libconfig-
model-dpkg-perl.

Hope this helps

Some clarifications:

There is for example a lot of logic in the package
DhMakePerl::Command::Packaging that I'd like to reuse for java packaging. For
that I'd need a reliable API and some logic would need to extracted from
larger functions into separate functions:

* get_developer(), get_wnpp() are fine for reuse
* fill_maintainer() has hardcoded reference to perl team
* set_package_name() contains logic to fall back to create a perl library
package name
* extract_desc() contains useful logic to format the long package description
* ...

I think it's fine to keep all this logic in the dh-make-perl package. It would
just be helpful to have a clear distinction between reusable code that could
be used for languages other than perl and code specific for packaging perl.

I'm just starting to learn perl, so it'll take some time until I can help with
this.

Regards,

Thomas Koch, http://www.koch.ro

-- 
This is Yosuf Mohammed from Emask Trading Group Turkey.
We will like to make an order. Please send us a quote, all our
requirements and specifications has been attached to the RFQ in
this mail.

Please kindly go through the RFQ and send us your price
quotations with
regards to the following notes:
- Item 3,14,22,30,40 and Item 26,27,38.


Best Regards
Yosuf Mohammed
Purchase/Sales Manager

EMASK SANAYI VE TICARET A.S.

Address: Akse Mahallesi 538. Sokak No:12

41420 Cayirova, KOCAELI/TURKIYE

Tel : +90 262 744 16 18

Fax : +90 262 744 41 50

Almost 10 years later, I think it is obvious the dh-make-perl authors
(me included) aren't very keen on separating the parts that are
specific to the Debian Perl Group and providing a more universal
library that can be used by others.

-=| Thomas Koch, 08.05.2013 19:49:19 +0200 |=-

Right. These are all good ideas. They "just" need someone to implement
them. We won't, it seems, so I am tagging the bugreport with 'help'.

If I was going to do it, I'd try to split all DPG-specific parts into
a ::Packaging::DPG or a similar package, sublcassing ::Packaging, and
change dh-make-perl to use that.

Then another tool, say dh-make-java, would need to provide
::Packaging::Java, subclassing ::Packaging with Java-specific
functions.

Perhaps there are some perl-specific things outside ::Packaging too.

The whole thing involves identifying domain specific parts, some
shuffling around and a lot of testing. I hope people who need this
functionality would be able to spend the time to try it.