Re: Importing pkg_module

[Landry Breuil]

On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> (some history)
> 
> During this summer the Jannis Tsaraias worked on the pkg_module, an
> automated port creation framework as a GSoC Project. The project
> succeeded, and Jannis stayed to maintain the code and accept patches
> from interested parties:
> 
> https://github.com/diethyl/pkg_module
> 
> (back to nowadays)
> 
> A few months went, and we're still at the same place. pkg_module
> proved to work by a few people already, and should be a nice addition
> for 5.9. So I want to move on and finally import it. I'm attaching the
> archive to be extracted under /usr/ports/infrastructure. After that
> just type something like "pkg_module ruby dbf" and see how easy it
> goes. :)
> 
> Personally I use it about once a month, saving a hour or two of manual
> work. In particular, I'm trying to reuse this code to make maintaining
> KDE Frameworks easier: doing things manually, I have to re-start
> porting a new version before finishing a previous one...
> 
> Any comments/suggestions/objections/okays?

Fwiw, i had a quick go at testing this because i wanted to play with
LastFM::Export, and it just did the right thing.

cd /tmp
git clone https://github.com/diethyl/pkg_module
cd pkg_module
perl -Ilib pkg_module p5 LastFM::Export

 lots of installing stuff from cpan already in the portstree...

and it generated the 4 missing ports i needed:

/usr/ports/mystuff/cpan/p5-MooseX-StrictConstructor
/usr/ports/mystuff/cpan/p5-Net-LastFM
/usr/ports/mystuff/cpan/p5-Data-Stream-Bulk
/usr/ports/mystuff/cpan/p5-LastFM-Export

With all the correct runtime dependencies - only missing thing was
p5-Test-Pod being a TDEP of p5-Net-LastFM but afaik this isnt handled
yet by the tool.

(oh, and of course in all this, the most awesome thing is that
LastFM::Export actually works - plenty of ideas flowing now...)

Landry

Re: Importing pkg_module

[Antoine Jacoutot]

On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> (some history)
> 
> During this summer the Jannis Tsaraias worked on the pkg_module, an
> automated port creation framework as a GSoC Project. The project
> succeeded, and Jannis stayed to maintain the code and accept patches
> from interested parties:
> 
> https://github.com/diethyl/pkg_module
> 
> (back to nowadays)
> 
> A few months went, and we're still at the same place. pkg_module
> proved to work by a few people already, and should be a nice addition
> for 5.9. So I want to move on and finally import it. I'm attaching the
> archive to be extracted under /usr/ports/infrastructure. After that
> just type something like "pkg_module ruby dbf" and see how easy it
> goes. :)
> 
> Personally I use it about once a month, saving a hour or two of manual
> work. In particular, I'm trying to reuse this code to make maintaining
> KDE Frameworks easier: doing things manually, I have to re-start
> porting a new version before finishing a previous one...
> 
> Any comments/suggestions/objections/okays?

I haven't looked at it yet but just one question: does it allow to *update* 
existing ports?
I wouldn't really be happy if it helped pushing even more orphaned ruby-* p5* 
... stuffs into the tree.

-- 
Antoine

Re: Importing pkg_module

[Vadim Zhukov]

17 дек. 2015 г. 11:12 пользователь "Antoine Jacoutot" 
написал:
>
> On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> > (some history)
> >
> > During this summer the Jannis Tsaraias worked on the pkg_module, an
> > automated port creation framework as a GSoC Project. The project
> > succeeded, and Jannis stayed to maintain the code and accept patches
> > from interested parties:
> >
> > https://github.com/diethyl/pkg_module
> >
> > (back to nowadays)
> >
> > A few months went, and we're still at the same place. pkg_module
> > proved to work by a few people already, and should be a nice addition
> > for 5.9. So I want to move on and finally import it. I'm attaching the
> > archive to be extracted under /usr/ports/infrastructure. After that
> > just type something like "pkg_module ruby dbf" and see how easy it
> > goes. :)
> >
> > Personally I use it about once a month, saving a hour or two of manual
> > work. In particular, I'm trying to reuse this code to make maintaining
> > KDE Frameworks easier: doing things manually, I have to re-start
> > porting a new version before finishing a previous one...
> >
> > Any comments/suggestions/objections/okays?
>
> I haven't looked at it yet but just one question: does it allow to
*update* existing ports?
> I wouldn't really be happy if it helped pushing even more orphaned ruby-*
p5* ... stuffs into the tree.

Not yet, unfortunately. Dreaming of it as well as you do. :)

Actually, since many autogenerated ports do not need tweaking at all, they
could be updated by replacing the whole directory. The only churn will
happen at $OpenBSD$ tags, but those are handled by CVS itself without
problems.

But the problems will arise in other ports, depending on old version and
changing behaviour (up to not being to run) with new ones. I don't see
simple solution here. :(

--
Vadim Zhukov

Re: Importing pkg_module

[Stuart Henderson]

On 2015/12/17 09:12, Antoine Jacoutot wrote:
> On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> > (some history)
> > 
> > During this summer the Jannis Tsaraias worked on the pkg_module, an
> > automated port creation framework as a GSoC Project. The project
> > succeeded, and Jannis stayed to maintain the code and accept patches
> > from interested parties:
> > 
> > https://github.com/diethyl/pkg_module
> > 
> > (back to nowadays)
> > 
> > A few months went, and we're still at the same place. pkg_module
> > proved to work by a few people already, and should be a nice addition
> > for 5.9. So I want to move on and finally import it. I'm attaching the
> > archive to be extracted under /usr/ports/infrastructure. After that
> > just type something like "pkg_module ruby dbf" and see how easy it
> > goes. :)
> > 
> > Personally I use it about once a month, saving a hour or two of manual
> > work. In particular, I'm trying to reuse this code to make maintaining
> > KDE Frameworks easier: doing things manually, I have to re-start
> > porting a new version before finishing a previous one...
> > 
> > Any comments/suggestions/objections/okays?
> 
> I haven't looked at it yet but just one question: does it allow to *update* 
> existing ports?
> I wouldn't really be happy if it helped pushing even more orphaned ruby-* p5* 
> ... stuffs into the tree.

That's a harder problem as you need to test dependent ports and figure
out whether test failures are new or already existed..

Importing pkg_module

[Vadim Zhukov]

(some history)

During this summer the Jannis Tsaraias worked on the pkg_module, an
automated port creation framework as a GSoC Project. The project
succeeded, and Jannis stayed to maintain the code and accept patches
from interested parties:

https://github.com/diethyl/pkg_module

(back to nowadays)

A few months went, and we're still at the same place. pkg_module
proved to work by a few people already, and should be a nice addition
for 5.9. So I want to move on and finally import it. I'm attaching the
archive to be extracted under /usr/ports/infrastructure. After that
just type something like "pkg_module ruby dbf" and see how easy it
goes. :)

Personally I use it about once a month, saving a hour or two of manual
work. In particular, I'm trying to reuse this code to make maintaining
KDE Frameworks easier: doing things manually, I have to re-start
porting a new version before finishing a previous one...

Any comments/suggestions/objections/okays?
--
  WBR,
  Vadim Zhukov

Re: Importing pkg_module

[Vadim Zhukov]

2015-12-16 22:33 GMT+03:00 Vadim Zhukov :
> (some history)
>
> During this summer the Jannis Tsaraias worked on the pkg_module, an
> automated port creation framework as a GSoC Project. The project
> succeeded, and Jannis stayed to maintain the code and accept patches
> from interested parties:
>
> https://github.com/diethyl/pkg_module
>
> (back to nowadays)
>
> A few months went, and we're still at the same place. pkg_module
> proved to work by a few people already, and should be a nice addition
> for 5.9. So I want to move on and finally import it. I'm attaching the
> archive to be extracted under /usr/ports/infrastructure. After that
> just type something like "pkg_module ruby dbf" and see how easy it
> goes. :)

And it works better if really attached - thank you, jca@!

> Personally I use it about once a month, saving a hour or two of manual
> work. In particular, I'm trying to reuse this code to make maintaining
> KDE Frameworks easier: doing things manually, I have to re-start
> porting a new version before finishing a previous one...
>
> Any comments/suggestions/objections/okays?

--
  WBR,
  Vadim Zhukov


infrastructure.tar.gz
Description: GNU Zip compressed data

Re: Importing pkg_module

[Vadim Zhukov]

2015-12-16 23:12 GMT+03:00 Landry Breuil :
> On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
>> (some history)
>>
>> During this summer the Jannis Tsaraias worked on the pkg_module, an
>> automated port creation framework as a GSoC Project. The project
>> succeeded, and Jannis stayed to maintain the code and accept patches
>> from interested parties:
>>
>> https://github.com/diethyl/pkg_module
>>
>> (back to nowadays)
>>
>> A few months went, and we're still at the same place. pkg_module
>> proved to work by a few people already, and should be a nice addition
>> for 5.9. So I want to move on and finally import it. I'm attaching the
>> archive to be extracted under /usr/ports/infrastructure. After that
>> just type something like "pkg_module ruby dbf" and see how easy it
>> goes. :)
>>
>> Personally I use it about once a month, saving a hour or two of manual
>> work. In particular, I'm trying to reuse this code to make maintaining
>> KDE Frameworks easier: doing things manually, I have to re-start
>> porting a new version before finishing a previous one...
>>
>> Any comments/suggestions/objections/okays?
>
> That sounds like a really nice addition, the 'pkg_module' naming is a
> bit weird but whatever..
>
> You could have mentioned that (as far i can gather from quickly looking
> at the code) it supports Ruby (forge? gems?), PyPI and CPAN as sources...
> And that it generates a _port_ (which means to keep local or to submit
> for import in cvs?), not a package - hence the confusing naming :)

Yep. I'm biased since I (as well as afresh1@) was involved in the
project as a mentor, and thus I missed those - meaningful! - points.
Thank you for pointing them out!

> But all this can be gathered from the manpage :)
>
> The only missing thing.. i dont see regress tests, nor a list of
> ports/packages tested working/non-working with it, to get an idea of its
> coverage of the corresponding 'native repositories'...

The list of "successfully tested on" is rather large, thus it was
dropped at some point in the past. :) And the SPECIALS file in repo
lists known items having problems (i.e., requiring manual porting
instead).

--
  WBR,
  Vadim Zhukov

Re: Importing pkg_module

[Landry Breuil]

On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> (some history)
> 
> During this summer the Jannis Tsaraias worked on the pkg_module, an
> automated port creation framework as a GSoC Project. The project
> succeeded, and Jannis stayed to maintain the code and accept patches
> from interested parties:
> 
> https://github.com/diethyl/pkg_module
> 
> (back to nowadays)
> 
> A few months went, and we're still at the same place. pkg_module
> proved to work by a few people already, and should be a nice addition
> for 5.9. So I want to move on and finally import it. I'm attaching the
> archive to be extracted under /usr/ports/infrastructure. After that
> just type something like "pkg_module ruby dbf" and see how easy it
> goes. :)
> 
> Personally I use it about once a month, saving a hour or two of manual
> work. In particular, I'm trying to reuse this code to make maintaining
> KDE Frameworks easier: doing things manually, I have to re-start
> porting a new version before finishing a previous one...
> 
> Any comments/suggestions/objections/okays?

That sounds like a really nice addition, the 'pkg_module' naming is a
bit weird but whatever..

You could have mentioned that (as far i can gather from quickly looking
at the code) it supports Ruby (forge? gems?), PyPI and CPAN as sources...
And that it generates a _port_ (which means to keep local or to submit
for import in cvs?), not a package - hence the confusing naming :)

But all this can be gathered from the manpage :)

The only missing thing.. i dont see regress tests, nor a list of
ports/packages tested working/non-working with it, to get an idea of its
coverage of the corresponding 'native repositories'...

Landry

Re: Importing pkg_module

[Giannis Tsaraias]

On Wed, Dec 16, 2015 at 11:19:13PM +0300, Vadim Zhukov wrote:
> 2015-12-16 23:12 GMT+03:00 Landry Breuil :
> > On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> >> (some history)
> >>
> >> During this summer the Jannis Tsaraias worked on the pkg_module, an
> >> automated port creation framework as a GSoC Project. The project
> >> succeeded, and Jannis stayed to maintain the code and accept patches
> >> from interested parties:
> >>
> >> https://github.com/diethyl/pkg_module
> >>
> >> (back to nowadays)
> >>
> >> A few months went, and we're still at the same place. pkg_module
> >> proved to work by a few people already, and should be a nice addition
> >> for 5.9. So I want to move on and finally import it. I'm attaching the
> >> archive to be extracted under /usr/ports/infrastructure. After that
> >> just type something like "pkg_module ruby dbf" and see how easy it
> >> goes. :)
> >>
> >> Personally I use it about once a month, saving a hour or two of manual
> >> work. In particular, I'm trying to reuse this code to make maintaining
> >> KDE Frameworks easier: doing things manually, I have to re-start
> >> porting a new version before finishing a previous one...
> >>
> >> Any comments/suggestions/objections/okays?
> >
> > That sounds like a really nice addition, the 'pkg_module' naming is a
> > bit weird but whatever..
> >
> > You could have mentioned that (as far i can gather from quickly looking
> > at the code) it supports Ruby (forge? gems?), PyPI and CPAN as sources...
> > And that it generates a _port_ (which means to keep local or to submit
> > for import in cvs?), not a package - hence the confusing naming :)
> 

PyPI.pm is currently a placeholder; I had some pieces of it working, but
thought I'd keep it out of the repo until its coverage gets closer to that
of CPAN or Ruby Gems.

> Yep. I'm biased since I (as well as afresh1@) was involved in the
> project as a mentor, and thus I missed those - meaningful! - points.
> Thank you for pointing them out!
> 
> > But all this can be gathered from the manpage :)
> >
> > The only missing thing.. i dont see regress tests, nor a list of
> > ports/packages tested working/non-working with it, to get an idea of its
> > coverage of the corresponding 'native repositories'...
> 
> The list of "successfully tested on" is rather large, thus it was
> dropped at some point in the past. :) And the SPECIALS file in repo
> lists known items having problems (i.e., requiring manual porting
> instead).
> 

That file could use some updates, which I've been meaning to do. One issue
worth mentioning is that currently there's no handling of modules that install
shared libraries, though I've recently started working on that.

I also have some useful feedback about CPAN by nigel@ that I haven't addressed 
yet.

Seeing that there's interest, I could resume working on this more actively. :)