[oi-dev] Unsubscribe

[h2o666@gmail]

Sent from my iPhone

> On Feb 6, 2016, at 4:00, oi-dev-request at openindiana.org wrote:
> 
> Send oi-dev mailing list submissions to
>    oi-dev at openindiana.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://openindiana.org/mailman/listinfo/oi-dev
> or, via email, send a message with subject or body 'help' to
>    oi-dev-request at openindiana.org
> 
> You can reach the person managing the list at
>    oi-dev-owner at openindiana.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of oi-dev digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Userland dev, Zone and processes (Jim Klimov)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 05 Feb 2016 21:04:51 +0100
> From: Jim Klimov <jimklimov at cos.ru>
> To: OpenIndiana Developer mailing list <oi-dev at openindiana.org>,
>    bentahyr at chez.com
> Subject: Re: [oi-dev] Userland dev, Zone and processes
> Message-ID: <9B266833-ED3D-4EA8-AA55-E93EC81A4295 at cos.ru>
> Content-Type: text/plain; charset=UTF-8
> 
> 5 ??????? 2016??. 1:48:27 CET, bentahyr at chez.com ?????:
>> Hi,
>> 
>> I created a zone with oi-userland dev and tools and I finally made my 2
>> first packages.
>> I gave up on cloning the dev zone (zoneadm clone doesn't work) to try
>> to install the package and relied VBox as I don't need much power to
>> test the package.
>> 
>> Now I would like to install these packages on my dev zone so I can work
>> on a third package depending on the 2 first ones but here I am with a
>> new issue. I can't seem to add publisher and use packages from my dev
>> zone.
>> Adding publisher is ok but when I issue the pkg install command I get :
>> 
>> -pkg install: Invalid child image publisher configuration.  Child image
>> publisher
>> -configuration must be a superset of the parent image publisher
>> configuration.
>> -Please update the child publisher configuration to match the parent. 
>> If the
>> -child image is a zone this can be done automatically by detaching and
>> -attaching the zone.
>> -
>> -The parent image has the following enabled publishers:
>> -    PUBLISHER 0: openindiana.org
>> -    PUBLISHER 1: hipster-encumbered
>> -
>> -The child image has the following enabled publishers:
>> -    PUBLISHER 0: userland
>> -    PUBLISHER 1: openindiana.org
>> -    PUBLISHER 2: hipster-encumbered
>> -    PUBLISHER 3: localhostoih
>> 
>> So I was wondering what am I doing wrong in the zone as it seems IPS is
>> highly tighten to the global zone. Is there a more independent way to
>> set the zone ?
>> 
>> Second question is what should be the process to add new packages to
>> userland on github ?
>> - open feature request on OI bug tracker ?
>> - pull request on github oi-userland repo ?
>> - mail to oi-dev ?
>> 
>> Best regards.
>> Ben
>> 
>> _______________________________________________
>> oi-dev mailing list
>> oi-dev at openindiana.org
>> http://openindiana.org/mailman/listinfo/oi-dev
> 
> regarding zone-cloning: seems like a bug, should be clonable. at worst you can manually snapshot and clone the zone's datasets and replicate the configuration in GZ /etc/zones/zonename.xml files and index listing there.
> 
> consider 'nlipkg' zone brand (IIRC) which is same as ipkg but unties these publisher requirements. 
> 
> procedure is gihubish - fork the repo, on github, clone your fork to your workstation, optionally make a branch for the new piece of work, develop, push back, make a PR against OpenJ diana/oi-userland, and prepare for discussions. Usually it boils down to common-style formality, sometimes suggestions on recipe implementation detail, and in the end you'd rebase so the changeset is one commit.
> 
> good luck,
> Jim
> --
> Typos courtesy of K-9 Mail on my Samsung Android
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev
> 
> ------------------------------
> 
> End of oi-dev Digest, Vol 66, Issue 3
> *************************************