Re: [OpenIndiana-discuss] SFW Packages left for migration

[Adam Števko]

Hi,

> On Oct 13, 2016, at 6:33 AM, Andreas Wacknitz  wrote:
> 
> Am 12.10.16 um 22:24 schrieb Adam Števko:
>> Hi,
>> 
>> 
>>> I would like to see is
>>>1. A page about build environment preparation, especially what packages 
>>> are needed (and how to install them) to build all userland packages
>>>Some words when you are trying to build in a zone. A downloadable 
>>> script would be nice…
>> https://wiki.openindiana.org/oi/Building+with+oi-userland 
>>  - this is the 
>> most up to date documentation how to get starting with oi-userland. It’s 
>> pretty much hidden as hipster content is not the first thing people will 
>> find. We need to fix this and mark/remove old content once and for all. 
>> However, wiki reorganization is more complex task and is out of scope of 
>> this email.
>> 
>> If you want faster way of getting up development environment setup, there is 
>> Vagrant (aimed at people not using OI as their primary system): This is 
>> currently the _FASTEST_ way to get started: 
>> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagrant.md
>> 
>> We could also write some script or copy/paste commands in some wiki page, 
>> but I always thought that zone setup was easy enough for everybody. Perhaps, 
>> my judgement is shrouded by the fact that I used zones basically daily.
>> 
>>>2. How and when to update the build environment.
>> Being rolling release, you update as often as you can.
> As far as I know you are not doing it with the jenkins env.
> Furthmore, sometimes there are new packages (or versions) that have to be 
> installed manually.

This happens when new package is added and is needed for building (gmake 
env-check/env-prep is not yet automatically called).


>> 
>>>3. A sample for a new package (steps that are needed) and a sample for 
>>> updating an existing package.
>> Usually, it’s enough to do following steps (supposing you are going to 
>> package component foo, which uses configure style Makefile). In components 
>> dir:
>> 
>> mkdir /foo
>> cp ../templates/configure.mk /foo/Makefile
>> cd /foo
>> vim Makefile
> And then? What to change in the Makefile? Eg. COMPONENT_REVISION.
> Creating a new package is just one thing. Taking a paking from Oracle 
> userland; from SFW, whatever source...
> What to do with pkgmogrify, what changes are needed in the p5m file?
> 
>> Templates can be found here: 
>> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/templates 
>> . As 
>> for other examples, it's best to look around components/ dir.
>> 
>>>4. Tips (collection of best practices and caveats).
>> - vagrant
> I am not familiar with vagrant; I am not sure whether you can expect that.

I don’t expect it and that’s the reason why it is documented in vagrant.md how 
to get it up and running.

> Plus, how to configure your own jenkins?
> 
>> - taking advantage of ZFS
> How so?

Rollbacking ZFS dataset of dirty workspace is usually faster than git clean 
-fdx, I used to use it occasionally.

>> - gmake env-prep/env-check
> My experience is that env-prep works only partially. Especially it failed to 
> prepare the whole env (gmake env-prep in root folder of the project).

Can you elaborate? How does it fail?

> 
>> These are more suitable for blogs. Anything in particular you are looking 
>> for?
> Blogs are a nice thing. Alas they are mostly static and a newcomer cannot 
> decide what is outdated and what not.
> This is also a problem with our wiki, especially because it deals with 
> several topics and versions (dev vs. hipster).
> 
> What happened to Michael's work? It seems to be stuck…

Michael’s work is pending the annoucement before we achieve one last thing, 
stay tuned ;)

Adam
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] SFW Packages left for migration; Xfig

[Carsten Grzemba]

For all who want to migrate from Xfig to LibreCAD: 
I added an import filter for Xfig PIC files on LibreCAD, not feature complete, 
but it is a begin.

On 12.10.16 13:52, "Udo Grabowski (IMK)"   wrote: 
> 
> On 12/10/2016 13:40, Udo Grabowski (IMK) wrote:
> >On 12/10/2016 13:54, Marc Lobelle wrote:
> >>.
> >>I'll see if I can make a package with a working version of xfig.
> >>
> >
> >Here are a set of patches I collected or made against xfig/transfig
> >3.2.5b/c, on OI 151a7 with SunStudio compiler. Obsolete netpbm calls
> >are exchanged for ImageMagick 'convert' (which then should be
> >a dependence for the xfig package) . Fonts are set to the
> >available scalable ones. /usr/openwin points to /usr/X11.
> >The fonts are still not completely working, but sufficent for
> >usual production use.
> 
> Uh oh, no attachments possible, so get them here:
> 
> 
> md5sum
> 2358e463482dfd596c28fafbfcd8aa8d transfig_patches_3.2.5c.gz
> d421a0d59dc49bc8d49fd1a5dba7283b xfig_patches_3.2.5b.gz
> -- 
> Dr.Udo Grabowski Inst.f.Meteorology & Climate Research IMK-ASF-SAT
> http://www.imk-asf.kit.edu/english/sat.php
> KIT - Karlsruhe Institute of Technology http://www.kit.edu
> Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] SFW Packages left for migration

[LGL Extern]

Hi 

I would like to publish some packages of our internal repository.
My p5m files are created with some script magic and contain user and group 
information in the actions.
I am wondering now why user and  group not defined in the existing p5m files 
e.g. sg3_utils.p5m?
When I have a look in the contents of the package in the repository user and 
group information are defined in the actions
Which part of the building process adds the use and group information?

Thanks

Andreas

-Ursprüngliche Nachricht-
Von: Adam Števko [mailto:adam.ste...@gmail.com] 
Gesendet: Donnerstag, 13. Oktober 2016 09:57
An: Discussion list for OpenIndiana
Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration

Hi,

> On Oct 13, 2016, at 6:33 AM, Andreas Wacknitz  wrote:
> 
> Am 12.10.16 um 22:24 schrieb Adam Števko:
>> Hi,
>> 
>> 
>>> I would like to see is
>>>1. A page about build environment preparation, especially what packages 
>>> are needed (and how to install them) to build all userland packages
>>>Some words when you are trying to build in a zone. A 
>>> downloadable script would be nice…
>> https://wiki.openindiana.org/oi/Building+with+oi-userland 
>>  - this is the 
>> most up to date documentation how to get starting with oi-userland. It’s 
>> pretty much hidden as hipster content is not the first thing people will 
>> find. We need to fix this and mark/remove old content once and for all. 
>> However, wiki reorganization is more complex task and is out of scope of 
>> this email.
>> 
>> If you want faster way of getting up development environment setup, 
>> there is Vagrant (aimed at people not using OI as their primary 
>> system): This is currently the _FASTEST_ way to get started: 
>> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagran
>> t.md
>> 
>> We could also write some script or copy/paste commands in some wiki page, 
>> but I always thought that zone setup was easy enough for everybody. Perhaps, 
>> my judgement is shrouded by the fact that I used zones basically daily.
>> 
>>>2. How and when to update the build environment.
>> Being rolling release, you update as often as you can.
> As far as I know you are not doing it with the jenkins env.
> Furthmore, sometimes there are new packages (or versions) that have to be 
> installed manually.

This happens when new package is added and is needed for building (gmake 
env-check/env-prep is not yet automatically called).


>> 
>>>3. A sample for a new package (steps that are needed) and a sample for 
>>> updating an existing package.
>> Usually, it’s enough to do following steps (supposing you are going to 
>> package component foo, which uses configure style Makefile). In components 
>> dir:
>> 
>> mkdir /foo
>> cp ../templates/configure.mk /foo/Makefile cd 
>> /foo vim Makefile
> And then? What to change in the Makefile? Eg. COMPONENT_REVISION.
> Creating a new package is just one thing. Taking a paking from Oracle 
> userland; from SFW, whatever source...
> What to do with pkgmogrify, what changes are needed in the p5m file?
> 
>> Templates can be found here: 
>> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/templates 
>> . As 
>> for other examples, it's best to look around components/ dir.
>> 
>>>4. Tips (collection of best practices and caveats).
>> - vagrant
> I am not familiar with vagrant; I am not sure whether you can expect that.

I don’t expect it and that’s the reason why it is documented in vagrant.md how 
to get it up and running.

> Plus, how to configure your own jenkins?
> 
>> - taking advantage of ZFS
> How so?

Rollbacking ZFS dataset of dirty workspace is usually faster than git clean 
-fdx, I used to use it occasionally.

>> - gmake env-prep/env-check
> My experience is that env-prep works only partially. Especially it failed to 
> prepare the whole env (gmake env-prep in root folder of the project).

Can you elaborate? How does it fail?

> 
>> These are more suitable for blogs. Anything in particular you are looking 
>> for?
> Blogs are a nice thing. Alas they are mostly static and a newcomer cannot 
> decide what is outdated and what not.
> This is also a problem with our wiki, especially because it deals with 
> several topics and versions (dev vs. hipster).
> 
> What happened to Michael's work? It seems to be stuck…

Michael’s work is pending the annoucement before we achieve one last thing, 
stay tuned ;)

Adam
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] SFW Packages left for migration

[Aurélien Larcher]

Hi,



> I am wondering now why user and  group not defined in the existing p5m
> files e.g. sg3_utils.p5m?
>

In most cases ownership and rights are applied with transforms, e.g. see:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/transforms/defaults

Of course you may need to override these defaults, for instance 'mode=0555'
for executables in non-standard paths.


> When I have a look in the contents of the package in the repository user
> and group information are defined in the actions
> Which part of the building process adds the use and group information?
>
> Thanks
>
> Andreas
>
> -Ursprüngliche Nachricht-
> Von: Adam Števko [mailto:adam.ste...@gmail.com]
> Gesendet: Donnerstag, 13. Oktober 2016 09:57
> An: Discussion list for OpenIndiana
> Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration
>
> Hi,
>
> > On Oct 13, 2016, at 6:33 AM, Andreas Wacknitz  wrote:
> >
> > Am 12.10.16 um 22:24 schrieb Adam Števko:
> >> Hi,
> >>
> >>
> >>> I would like to see is
> >>>1. A page about build environment preparation, especially what
> packages are needed (and how to install them) to build all userland packages
> >>>Some words when you are trying to build in a zone. A
> >>> downloadable script would be nice…
> >> https://wiki.openindiana.org/oi/Building+with+oi-userland <
> https://wiki.openindiana.org/oi/Building+with+oi-userland> - this is the
> most up to date documentation how to get starting with oi-userland. It’s
> pretty much hidden as hipster content is not the first thing people will
> find. We need to fix this and mark/remove old content once and for all.
> However, wiki reorganization is more complex task and is out of scope of
> this email.
> >>
> >> If you want faster way of getting up development environment setup,
> >> there is Vagrant (aimed at people not using OI as their primary
> >> system): This is currently the _FASTEST_ way to get started:
> >> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagran
> >> t.md
> >>
> >> We could also write some script or copy/paste commands in some wiki
> page, but I always thought that zone setup was easy enough for everybody.
> Perhaps, my judgement is shrouded by the fact that I used zones basically
> daily.
> >>
> >>>2. How and when to update the build environment.
> >> Being rolling release, you update as often as you can.
> > As far as I know you are not doing it with the jenkins env.
> > Furthmore, sometimes there are new packages (or versions) that have to
> be installed manually.
>
> This happens when new package is added and is needed for building (gmake
> env-check/env-prep is not yet automatically called).
>
>
> >>
> >>>3. A sample for a new package (steps that are needed) and a sample
> for updating an existing package.
> >> Usually, it’s enough to do following steps (supposing you are going to
> package component foo, which uses configure style Makefile). In components
> dir:
> >>
> >> mkdir /foo
> >> cp ../templates/configure.mk /foo/Makefile cd
> >> /foo vim Makefile
> > And then? What to change in the Makefile? Eg. COMPONENT_REVISION.
> > Creating a new package is just one thing. Taking a paking from Oracle
> userland; from SFW, whatever source...
> > What to do with pkgmogrify, what changes are needed in the p5m file?
> >
> >> Templates can be found here: https://github.com/
> OpenIndiana/oi-userland/tree/oi/hipster/templates  OpenIndiana/oi-userland/tree/oi/hipster/templates>. As for other
> examples, it's best to look around components/ dir.
> >>
> >>>4. Tips (collection of best practices and caveats).
> >> - vagrant
> > I am not familiar with vagrant; I am not sure whether you can expect
> that.
>
> I don’t expect it and that’s the reason why it is documented in vagrant.md
> how to get it up and running.
>
> > Plus, how to configure your own jenkins?
> >
> >> - taking advantage of ZFS
> > How so?
>
> Rollbacking ZFS dataset of dirty workspace is usually faster than git
> clean -fdx, I used to use it occasionally.
>
> >> - gmake env-prep/env-check
> > My experience is that env-prep works only partially. Especially it
> failed to prepare the whole env (gmake env-prep in root folder of the
> project).
>
> Can you elaborate? How does it fail?
>
> >
> >> These are more suitable for blogs. Anything in particular you are
> looking for?
> > Blogs are a nice thing. Alas they are mostly static and a newcomer
> cannot decide what is outdated and what not.
> > This is also a problem with our wiki, especially because it deals with
> several topics and versions (dev vs. hipster).
> >
> > What happened to Michael's work? It seems to be stuck…
>
> Michael’s work is pending the annoucement before we achieve one last
> thing, stay tuned ;)
>
> Adam
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> ___

Re: [OpenIndiana-discuss] SFW Packages left for migration

[LGL Extern]

Hi,

Since yesterday I know how to use transform.

I had a look in sg3_utils.p5m and tried to understand where user and groups are 
set.

The line
 default mangler.man.stability uncommitted>
don't set the attributes for user and group.

May be the lines call some magic
...
file sg3_utils-exec_attr path=etc/security/exec_attr.d/system:storage:sg3_utils
file sg3_utils-prof_attr path=etc/security/prof_attr.d/system:storage:sg3_utils
...

Thanks

Andreas

-Ursprüngliche Nachricht-
Von: Aurélien Larcher [mailto:aurelien.larc...@gmail.com] 
Gesendet: Donnerstag, 13. Oktober 2016 11:21
An: Discussion list for OpenIndiana
Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration

Hi,



> I am wondering now why user and  group not defined in the existing p5m 
> files e.g. sg3_utils.p5m?
>

In most cases ownership and rights are applied with transforms, e.g. see:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/transforms/defaults

Of course you may need to override these defaults, for instance 'mode=0555'
for executables in non-standard paths.


> When I have a look in the contents of the package in the repository 
> user and group information are defined in the actions Which part of 
> the building process adds the use and group information?
>
> Thanks
>
> Andreas
>
> -Ursprüngliche Nachricht-
> Von: Adam Števko [mailto:adam.ste...@gmail.com]
> Gesendet: Donnerstag, 13. Oktober 2016 09:57
> An: Discussion list for OpenIndiana
> Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration
>
> Hi,
>
> > On Oct 13, 2016, at 6:33 AM, Andreas Wacknitz  wrote:
> >
> > Am 12.10.16 um 22:24 schrieb Adam Števko:
> >> Hi,
> >>
> >>
> >>> I would like to see is
> >>>1. A page about build environment preparation, especially what
> packages are needed (and how to install them) to build all userland 
> packages
> >>>Some words when you are trying to build in a zone. A 
> >>> downloadable script would be nice…
> >> https://wiki.openindiana.org/oi/Building+with+oi-userland <
> https://wiki.openindiana.org/oi/Building+with+oi-userland> - this is 
> the most up to date documentation how to get starting with 
> oi-userland. It’s pretty much hidden as hipster content is not the 
> first thing people will find. We need to fix this and mark/remove old content 
> once and for all.
> However, wiki reorganization is more complex task and is out of scope 
> of this email.
> >>
> >> If you want faster way of getting up development environment setup, 
> >> there is Vagrant (aimed at people not using OI as their primary
> >> system): This is currently the _FASTEST_ way to get started:
> >> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagr
> >> an
> >> t.md
> >>
> >> We could also write some script or copy/paste commands in some wiki
> page, but I always thought that zone setup was easy enough for everybody.
> Perhaps, my judgement is shrouded by the fact that I used zones 
> basically daily.
> >>
> >>>2. How and when to update the build environment.
> >> Being rolling release, you update as often as you can.
> > As far as I know you are not doing it with the jenkins env.
> > Furthmore, sometimes there are new packages (or versions) that have 
> > to
> be installed manually.
>
> This happens when new package is added and is needed for building 
> (gmake env-check/env-prep is not yet automatically called).
>
>
> >>
> >>>3. A sample for a new package (steps that are needed) and a 
> >>> sample
> for updating an existing package.
> >> Usually, it’s enough to do following steps (supposing you are going 
> >> to
> package component foo, which uses configure style Makefile). In 
> components
> dir:
> >>
> >> mkdir /foo
> >> cp ../templates/configure.mk /foo/Makefile cd 
> >> /foo vim Makefile
> > And then? What to change in the Makefile? Eg. COMPONENT_REVISION.
> > Creating a new package is just one thing. Taking a paking from 
> > Oracle
> userland; from SFW, whatever source...
> > What to do with pkgmogrify, what changes are needed in the p5m file?
> >
> >> Templates can be found here: https://github.com/
> OpenIndiana/oi-userland/tree/oi/hipster/templates  OpenIndiana/oi-userland/tree/oi/hipster/templates>. As for other 
> examples, it's best to look around components/ dir.
> >>
> >>>4. Tips (collection of best practices and caveats).
> >> - vagrant
> > I am not familiar with vagrant; I am not sure whether you can expect
> that.
>
> I don’t expect it and that’s the reason why it is documented in 
> vagrant.md how to get it up and running.
>
> > Plus, how to configure your own jenkins?
> >
> >> - taking advantage of ZFS
> > How so?
>
> Rollbacking ZFS dataset of dirty workspace is usually faster than git 
> clean -fdx, I used to use it occasionally.
>
> >> - gmake env-prep/env-check
> > My experience is that env-prep works only partially. Especially it
> failed to prepare the whole env (gmake env-prep in root folder of the 
> project).
>
> C

Re: [OpenIndiana-discuss] SFW Packages left for migration

[Aurélien Larcher]

On Thu, Oct 13, 2016 at 11:27 AM, Grüninger, Andreas (LGL Extern) <
andreas.gruenin...@lgl.bwl.de> wrote:

> Hi,
>
> Since yesterday I know how to use transform.
>
> I had a look in sg3_utils.p5m and tried to understand where user and
> groups are set.
>
> The line
>  default mangler.man.stability
> uncommitted>
> don't set the attributes for user and group.
>
> May be the lines call some magic
> ...
> file sg3_utils-exec_attr path=etc/security/exec_attr.d/
> system:storage:sg3_utils
> file sg3_utils-prof_attr path=etc/security/prof_attr.d/
> system:storage:sg3_utils
> ...
>

No no the transforms in the directory I linked are the ones called.

You can see here:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/ips.mk

defines the variable PUBLISH_TRANSFORMS containing the list of transform
files passed to pkgmogrify.



>
> Thanks
>
> Andreas
>
> -Ursprüngliche Nachricht-
> Von: Aurélien Larcher [mailto:aurelien.larc...@gmail.com]
> Gesendet: Donnerstag, 13. Oktober 2016 11:21
> An: Discussion list for OpenIndiana
> Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration
>
> Hi,
>
>
>
> > I am wondering now why user and  group not defined in the existing p5m
> > files e.g. sg3_utils.p5m?
> >
>
> In most cases ownership and rights are applied with transforms, e.g. see:
>
> https://github.com/OpenIndiana/oi-userland/blob/
> oi/hipster/transforms/defaults
>
> Of course you may need to override these defaults, for instance 'mode=0555'
> for executables in non-standard paths.
>
>
> > When I have a look in the contents of the package in the repository
> > user and group information are defined in the actions Which part of
> > the building process adds the use and group information?
> >
> > Thanks
> >
> > Andreas
> >
> > -Ursprüngliche Nachricht-
> > Von: Adam Števko [mailto:adam.ste...@gmail.com]
> > Gesendet: Donnerstag, 13. Oktober 2016 09:57
> > An: Discussion list for OpenIndiana
> > Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration
> >
> > Hi,
> >
> > > On Oct 13, 2016, at 6:33 AM, Andreas Wacknitz 
> wrote:
> > >
> > > Am 12.10.16 um 22:24 schrieb Adam Števko:
> > >> Hi,
> > >>
> > >>
> > >>> I would like to see is
> > >>>1. A page about build environment preparation, especially what
> > packages are needed (and how to install them) to build all userland
> > packages
> > >>>Some words when you are trying to build in a zone. A
> > >>> downloadable script would be nice…
> > >> https://wiki.openindiana.org/oi/Building+with+oi-userland <
> > https://wiki.openindiana.org/oi/Building+with+oi-userland> - this is
> > the most up to date documentation how to get starting with
> > oi-userland. It’s pretty much hidden as hipster content is not the
> > first thing people will find. We need to fix this and mark/remove old
> content once and for all.
> > However, wiki reorganization is more complex task and is out of scope
> > of this email.
> > >>
> > >> If you want faster way of getting up development environment setup,
> > >> there is Vagrant (aimed at people not using OI as their primary
> > >> system): This is currently the _FASTEST_ way to get started:
> > >> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/vagr
> > >> an
> > >> t.md
> > >>
> > >> We could also write some script or copy/paste commands in some wiki
> > page, but I always thought that zone setup was easy enough for everybody.
> > Perhaps, my judgement is shrouded by the fact that I used zones
> > basically daily.
> > >>
> > >>>2. How and when to update the build environment.
> > >> Being rolling release, you update as often as you can.
> > > As far as I know you are not doing it with the jenkins env.
> > > Furthmore, sometimes there are new packages (or versions) that have
> > > to
> > be installed manually.
> >
> > This happens when new package is added and is needed for building
> > (gmake env-check/env-prep is not yet automatically called).
> >
> >
> > >>
> > >>>3. A sample for a new package (steps that are needed) and a
> > >>> sample
> > for updating an existing package.
> > >> Usually, it’s enough to do following steps (supposing you are going
> > >> to
> > package component foo, which uses configure style Makefile). In
> > components
> > dir:
> > >>
> > >> mkdir /foo
> > >> cp ../templates/configure.mk /foo/Makefile cd
> > >> /foo vim Makefile
> > > And then? What to change in the Makefile? Eg. COMPONENT_REVISION.
> > > Creating a new package is just one thing. Taking a paking from
> > > Oracle
> > userland; from SFW, whatever source...
> > > What to do with pkgmogrify, what changes are needed in the p5m file?
> > >
> > >> Templates can be found here: https://github.com/
> > OpenIndiana/oi-userland/tree/oi/hipster/templates  > OpenIndiana/oi-userland/tree/oi/hipster/templates>. As for other
> > examples, it's best to look around components/ dir.
> > >>
> > >>>4. Tips (collection of best practices and caveats).
> > >> - 

Re: [OpenIndiana-discuss] SFW Packages left for migration

[LGL Extern]

Hi Aurélian

Thanks a lot for the link.

Andreas

-Ursprüngliche Nachricht-
Von: Aurélien Larcher [mailto:aurelien.larc...@gmail.com] 
Gesendet: Donnerstag, 13. Oktober 2016 11:44
An: Discussion list for OpenIndiana
Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration

On Thu, Oct 13, 2016 at 11:27 AM, Grüninger, Andreas (LGL Extern) < 
andreas.gruenin...@lgl.bwl.de> wrote:

> Hi,
>
> Since yesterday I know how to use transform.
>
> I had a look in sg3_utils.p5m and tried to understand where user and 
> groups are set.
>
> The line
>  default mangler.man.stability
> uncommitted>
> don't set the attributes for user and group.
>
> May be the lines call some magic
> ...
> file sg3_utils-exec_attr path=etc/security/exec_attr.d/ 
> system:storage:sg3_utils file sg3_utils-prof_attr 
> path=etc/security/prof_attr.d/ system:storage:sg3_utils ...
>

No no the transforms in the directory I linked are the ones called.

You can see here:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/ips.mk

defines the variable PUBLISH_TRANSFORMS containing the list of transform files 
passed to pkgmogrify.



>
> Thanks
>
> Andreas
>
> -Ursprüngliche Nachricht-
> Von: Aurélien Larcher [mailto:aurelien.larc...@gmail.com]
> Gesendet: Donnerstag, 13. Oktober 2016 11:21
> An: Discussion list for OpenIndiana
> Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration
>
> Hi,
>
>
>
> > I am wondering now why user and  group not defined in the existing 
> > p5m files e.g. sg3_utils.p5m?
> >
>
> In most cases ownership and rights are applied with transforms, e.g. see:
>
> https://github.com/OpenIndiana/oi-userland/blob/
> oi/hipster/transforms/defaults
>
> Of course you may need to override these defaults, for instance 'mode=0555'
> for executables in non-standard paths.
>
>
> > When I have a look in the contents of the package in the repository 
> > user and group information are defined in the actions Which part of 
> > the building process adds the use and group information?
> >
> > Thanks
> >
> > Andreas
> >
> > -Ursprüngliche Nachricht-
> > Von: Adam Števko [mailto:adam.ste...@gmail.com]
> > Gesendet: Donnerstag, 13. Oktober 2016 09:57
> > An: Discussion list for OpenIndiana
> > Betreff: Re: [OpenIndiana-discuss] SFW Packages left for migration
> >
> > Hi,
> >
> > > On Oct 13, 2016, at 6:33 AM, Andreas Wacknitz 
> wrote:
> > >
> > > Am 12.10.16 um 22:24 schrieb Adam Števko:
> > >> Hi,
> > >>
> > >>
> > >>> I would like to see is
> > >>>1. A page about build environment preparation, especially 
> > >>> what
> > packages are needed (and how to install them) to build all userland 
> > packages
> > >>>Some words when you are trying to build in a zone. A 
> > >>> downloadable script would be nice…
> > >> https://wiki.openindiana.org/oi/Building+with+oi-userland <
> > https://wiki.openindiana.org/oi/Building+with+oi-userland> - this is 
> > the most up to date documentation how to get starting with 
> > oi-userland. It’s pretty much hidden as hipster content is not the 
> > first thing people will find. We need to fix this and mark/remove 
> > old
> content once and for all.
> > However, wiki reorganization is more complex task and is out of 
> > scope of this email.
> > >>
> > >> If you want faster way of getting up development environment 
> > >> setup, there is Vagrant (aimed at people not using OI as their 
> > >> primary
> > >> system): This is currently the _FASTEST_ way to get started:
> > >> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/doc/va
> > >> gr
> > >> an
> > >> t.md
> > >>
> > >> We could also write some script or copy/paste commands in some 
> > >> wiki
> > page, but I always thought that zone setup was easy enough for everybody.
> > Perhaps, my judgement is shrouded by the fact that I used zones 
> > basically daily.
> > >>
> > >>>2. How and when to update the build environment.
> > >> Being rolling release, you update as often as you can.
> > > As far as I know you are not doing it with the jenkins env.
> > > Furthmore, sometimes there are new packages (or versions) that 
> > > have to
> > be installed manually.
> >
> > This happens when new package is added and is needed for building 
> > (gmake env-check/env-prep is not yet automatically called).
> >
> >
> > >>
> > >>>3. A sample for a new package (steps that are needed) and a 
> > >>> sample
> > for updating an existing package.
> > >> Usually, it’s enough to do following steps (supposing you are 
> > >> going to
> > package component foo, which uses configure style Makefile). In 
> > components
> > dir:
> > >>
> > >> mkdir /foo
> > >> cp ../templates/configure.mk /foo/Makefile cd 
> > >> /foo vim Makefile
> > > And then? What to change in the Makefile? Eg. COMPONENT_REVISION.
> > > Creating a new package is just one thing. Taking a paking from 
> > > Oracle
> > userland; from SFW, whatever source...
> > > What to do with pkgmogrify, what changes are needed in the p5