[pacman-dev] Better handling for domain-specific packages (rubygems, cpan, ...)

Florian Pritz bluewind at xinu.at
Thu Jun 27 08:36:54 EDT 2013

On 27.06.2013 03:14, Allan McRae wrote:
> On 27/06/13 07:26, Anatol Pomozov wrote:
>> Could this situation be improved? Could Arch generate packages
>> automatically or semiautomatically from domain-specific package?
>> Something like *_PACKAGE macro for PKGBUILD:
> Check out makepkg-template in the git repo.

I'm planing on figuring out how to create a template for cpan packages
that will only require the module name and the version.

I'll probably use http://api.metacpan.org to get the metadata while
building (but relying on external services for that needs discussion
first) and then there will be a (hopefully) simple script that bumps the
package version to the most recent cpan release.

This is out of the scope of this list though and I'm not yet ready for
much discussion on the matter.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20130627/672ac545/attachment.asc>

More information about the pacman-dev mailing list