Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bundle:: and Task:: modules don't work as AUR packages. #2

Open
juster opened this issue Mar 18, 2010 · 2 comments
Open

Bundle:: and Task:: modules don't work as AUR packages. #2

juster opened this issue Mar 18, 2010 · 2 comments
Labels

Comments

@juster
Copy link
Owner

juster commented Mar 18, 2010

When trying to create an AUR package for a Bundle:: or Task:: module things go horribly wrong...

Bundle:: Modules

Bundle:: modules are .pm files that mostly just contain POD documentation. The POD gives a list of modules to install in a "bundle".

The problem is the CPAN client (or CPANPLUS) must parse the Bundle's POD and then go installing the modules. This doesn't happen when you create a PKGBUILD for an AUR package.

Task:: Modules

Task:: was created to solve Bundle::'s shortcomings. Task::'s can be installed standalone, without a CPAN client. They do this using Module::Install. Unfortunately Module::Install does not package modules when it installs them (and their dependencies)!

@juster
Copy link
Owner Author

juster commented Apr 10, 2010

Solution for Task::

Figure out how to write a plugin for Module::Install. The locally installed version of Module::Install seems to override the included copy of Module::Install. So if we install a plugin for M::I it should automagically kick in. If this is even possible of course...

@juster
Copy link
Owner Author

juster commented Apr 10, 2010

Solution for Bundle::'s

We must treat Bundle's specially and add more logic to CPANPLUS::Dist::Arch. There are two solutions I have thought of so far:

Hard

Bundle each module distribution, including the source file in the PKGBUILD's source array, and having a separate perl Makefile.PL sequence for each one.

Soft

Parse each distribution name that is provided by the Bundle::. Actually I think CPANPLUS can do this for us. TODO: Figure out how CPANPLUS provides this info, convert them to package names, and assign them to the dependency array.

I like the Soft solution better...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant