Add packages to the gemspec

[amonaksis]

It closes #6 .

How to test it:

rake build 
gem unpack pkg/<generated>.gem

Check the folder name inside the unpackaged folder you should see packages folder with all package definitions.

[yrashk]

Thank you for the contribution!

I think I understand where this comes from – there's an underemphasized expectation that pgpm will look for the packages directory in the current work directory.

I don't think we should be putting extension definitions into the pgpm package because that'll mean we have to cut a new release every time anything's changed about this. This will conflate pgpm's own versioning with package versioning and require updated at all times.

The expected model is to supply the packages directory (it's also configurable in the pgpm tool) to the script. Do you have any ideas on how to make this whole workflow more natural and better understood?

[jonatas]

I was testing this with @amonaksis last Friday and I suggested this fix.

My understanding was that the built image should contain or fetch the latest release, and have the ability to also sync it locally. The interesting part is that we ran the command in the pgpm directory, but the packages weren't added.

Is there any recommendation on how to bind the packages folder or why it was not working from the official image?

[yrashk]

It looks in the current directory by default. Were you running it as ./exe/pgpm ...?