Thread: [Module-build-general] Re: Module Build 0.16 PPM
Status: Beta
Brought to you by:
kwilliams
Menu
▾
▴
module-build-general
|
From: Ken W. <ke...@ma...> - 2003-03-04 20:48:10
|
On Tuesday, March 4, 2003, at 02:38 PM, Bri...@AR... wrote: > Ken - > > I downloaded and installed Module::Build 0.16 on my Win32 ActiveState > Perl > 5.6 without a hitch. Great work! Much smoother than the 0.15 > installation I conversed with you about last month. > > I've attached a PPM package for Win32 ActiveState Perl 5.6 > installation of > Module::Build 0.16 -- Feel free to use it and distribute if you like. > Note, my crappy mailer (Lotus Notes) will probably munge the name to > 8.3 - > it's originally 'Module-Build-0.16_ppm.tar.gz' > > I'm not sure what's involved (too busy to dig in right now), but > supporting a build target of 'ppd' mirroring the functionality of the > existing MakeMaker system will ease generation of these package for > future > users of Module::Build. Awesome, thanks for testing and for the PPM. I'm quite interested in supporting a 'ppd' action (both for M::B itself and for other modules built using M::B), so at some point I'll want to figure out how to do this properly. How did you create this one? Where's the best place for me to put the PPM tarball? I can certainly upload it to my CPAN directory, should I also see about getting it in the ActiveState repository or something? -Ken |
|
From: Randy W. S. <Ra...@Th...> - 2003-03-12 05:55:04
|
ActiveState just opened a new list for PPM which I've CC'd so that maybe Jan Dubois and Co. can offer some suggestions/insights. On 3/4/2003 3:48 PM, Ken Williams wrote: > > On Tuesday, March 4, 2003, at 02:38 PM, Bri...@AR... wrote: > >> Ken - >> >> I downloaded and installed Module::Build 0.16 on my Win32 ActiveState >> Perl >> 5.6 without a hitch. Great work! Much smoother than the 0.15 >> installation I conversed with you about last month. >> >> I've attached a PPM package for Win32 ActiveState Perl 5.6 >> installation of >> Module::Build 0.16 -- Feel free to use it and distribute if you like. >> Note, my crappy mailer (Lotus Notes) will probably munge the name to >> 8.3 - >> it's originally 'Module-Build-0.16_ppm.tar.gz' >> >> I'm not sure what's involved (too busy to dig in right now), but >> supporting a build target of 'ppd' mirroring the functionality of the >> existing MakeMaker system will ease generation of these package for >> future >> users of Module::Build. > > > Awesome, thanks for testing and for the PPM. I'm quite interested in > supporting a 'ppd' action (both for M::B itself and for other modules > built using M::B), so at some point I'll want to figure out how to do > this properly. How did you create this one? The ppd target prints a simple xml file describing the distribution for PPM. The format is based on the Open Software Description format <http://www.w3.org/TR/NOTE-OSD.html> The only problem with the ppd target under M::B is specifying prereqs- How will M::B's more dynamic & flexible dependencies be specified in the static ppd file? (rf. <http://sourceforge.net/mailarchive/forum.php ?thread_id=1676522&forum_id=10905> ). > Where's the best place for me to put the PPM tarball? I can certainly > upload it to my CPAN directory, should I also see about getting it in > the ActiveState repository or something? > > -Ken ActiveState regularly performs an automated build and packaging (PPM) of modules on CPAN. If the module builds without problem it is automatically placed in their repository (as M::B currently is for most AS supported archs). It looks like you can check the status at <http://ppm-ia.activestate.com> Currently there is only one failure: perl-5.8 on hpux-ia64-lp64 (Hmm, it passes with perl-5.6 on same arch; Unfortunately there doesn't seem to be any log for the failures.) Randy. |
|
From: Ken W. <ke...@ma...> - 2003-03-12 22:54:15
|
On Tuesday, March 11, 2003, at 11:54 PM, Randy W. Sims wrote: > ActiveState just opened a new list for PPM which I've CC'd so that > maybe Jan Dubois and Co. can offer some suggestions/insights. Cool. > The ppd target prints a simple xml file describing the distribution > for PPM. The format is based on the Open Software Description format > <http://www.w3.org/TR/NOTE-OSD.html> > Thanks for the reference, I hadn't seen that yet. > The only problem with the ppd target under M::B is specifying prereqs- > How will M::B's more dynamic & flexible dependencies be specified in > the static ppd file? (rf. > <http://sourceforge.net/mailarchive/forum.php > ?thread_id=1676522&forum_id=10905> > ). Yeah, that may be an issue. I'd like to get the META.yml file to line up better, at least conceptually, with the PPD file. > ActiveState regularly performs an automated build and packaging (PPM) > of modules on CPAN. If the module builds without problem it is > automatically placed in their repository (as M::B currently is for > most AS supported archs). It looks like you can check the status at > <http://ppm-ia.activestate.com> > > Currently there is only one failure: perl-5.8 on hpux-ia64-lp64 (Hmm, > it passes with perl-5.6 on same arch; Unfortunately there doesn't seem > to be any log for the failures.) Hmm, I wonder whether there's some way to see the output? It would be helpful if they were linked. Anyone at the PPM list have the power to make it so? -Ken |
|
From: Jan D. <ja...@Ac...> - 2003-03-12 23:43:25
|
On Wed, 12 Mar 2003 16:54:01 -0600, Ken Williams <ke...@ma...> wrote: [You need to subscribe to the mailing list in order to post here; it is not a moderated list, so messages from non-subscribers waiting in the moderation queue may take a looooong time to appear on the list.] >> ActiveState regularly performs an automated build and packaging (PPM) >> of modules on CPAN. If the module builds without problem it is >> automatically placed in their repository (as M::B currently is for >> most AS supported archs). It looks like you can check the status at >> <http://ppm-ia.activestate.com> >> >> Currently there is only one failure: perl-5.8 on hpux-ia64-lp64 (Hmm, >> it passes with perl-5.6 on same arch; Unfortunately there doesn't seem >> to be any log for the failures.) The automated build system is currently offline due to maintenance. It should get online again soonish (this month). >Hmm, I wonder whether there's some way to see the output? It would be >helpful if they were linked. Anyone at the PPM list have the power to >make it so? Yes, we are going to do that too. Cheers, -Jan |
Thanks for helping keep SourceForge clean.
X