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

2016-10-13 Thread 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

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

2016-10-13 Thread 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

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

2016-10-13 Thread 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 <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 vagr

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

2016-10-13 Thread 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 <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
> lo

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

2016-10-13 Thread 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 
>> <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 
>> <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; Xfig

2016-10-13 Thread 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

2016-10-13 Thread 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

2016-10-12 Thread Aurélien Larcher 
> Both your links are hidden treasures. But how should a newcomer find them?
>

This was just a work-in-progress intended to be polished for the
announcement of OpenIndiana Docs.
If anyone has time and feels like copying my notes to the Wiki then it
would be nice.
Just (below) zero time available right now ...


>
> Building in a zone has some pros and cons. For me one of the pros is that
> I can
> move my build env easily to a new machine. And yes, there is some burden.
> If it is not recommended, it should be stated somewhere. Otherwise some
> might
> fall into this trap...
>

For "casual" packaging on non-critical systems and provided that you can
create backup BE, I really do not see the point in using a zone; especially
when zones can fail to update or get stuck at unmount and become a
nightmare for non-experienced people.

Kind regards

Aurélien


>
> Regards,
>
> Andreas
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

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

2016-10-12 Thread Andreas Wacknitz 

Am 12.10.16 um 22:10 schrieb Aurélien Larcher:

On Wed, Oct 12, 2016 at 10:08 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:



On Wed, Oct 12, 2016 at 10:01 PM, Andreas Wacknitz 
wrote:



Am 12.10.16 um 12:48 schrieb Adam Števko:

Hi,

On 12 Oct 2016, at 13:54, Marc Lobelle 

wrote:

On 11/10/16 18:19, Aurélien Larcher wrote:

Hi,
here is a short list of packages looking for adoption by a nice
maintainer:

benchmark/iozone
developer/fakeroot
developer/versioning/guilt
editor/bvi
editor/jedit
image/virtualgl
library/idnkit
library/libosip2
library/xmlrpc-c
shell/shmux
terminal/roxterm
web/aget

Considering that we have been talking about this for several months,
if nobody is interested in updating them right now, I guess they
should simply be deprecated instead of carrying old versions around.

Aurélien

Some old open source programs are not maintained any more but they do

well what they are supposed to do. I think xfig is in this case. However
they are still usefull and used. It is always a loss of time to have to
find a source and recompile it when you install a new computer with a
recent OS distribution (such as OI-Hipster1604).

There are also programs that are still maintained but of which an old
version is in OI, such as cups: it is better to have an old cups than no
cups at all.

As long as such programs work I would keep them in distributions. If
one does not like to have them with the others, they could somehow be
flagged as old.

I'll see if I can make a package with a working version of xfig. Can
you point me to an howto (assuming I have  a working compiled version for
OI).

Thanks

Marc


https://wiki.openindiana.org/oi/Building+with+oi-userland

For packaging tips look for examples in other components. Also write
down any problems with the quality of the documentation, so we can make it
better.

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


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...
 2. How and when to update the build environment.
 3. A sample for a new package (steps that are needed) and a sample
for updating an existing package.
 4. Tips (collection of best practices and caveats).

I think all this would make it easier for newcomers.


I need to update it but this is a start:

https://openindiana.github.io/oi-docs/dev/userland/

It is missing the recent addition of REQUIRED_PACKAGES and pre-publish.



Gh all the = where turned into # ...

http://hub.openindiana.ninja/?q=content/quick-start-oi-userland



For simple packaging tasks and provided that the system is plain Hipster,
installation in a zone is IMHO an unnecessary burden.



Both your links are hidden treasures. But how should a newcomer find them?

Building in a zone has some pros and cons. For me one of the pros is 
that I can

move my build env easily to a new machine. And yes, there is some burden.
If it is not recommended, it should be stated somewhere. Otherwise some 
might

fall into this trap...

Regards,
Andreas


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

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

2016-10-12 Thread Andreas Wacknitz 

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.





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.
Plus, how to configure your own jenkins?


- taking advantage of ZFS

How so?


- 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).



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...



Cheers,
Adam
___


Regards,
Andreas

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

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

2016-10-12 Thread 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.

>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

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
- taking advantage of ZFS
- gmake env-prep/env-check

These are more suitable for blogs. Anything in particular you are looking for?

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

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

2016-10-12 Thread Aurélien Larcher 
On Wed, Oct 12, 2016 at 10:08 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
> On Wed, Oct 12, 2016 at 10:01 PM, Andreas Wacknitz 
> wrote:
>
>>
>>
>> Am 12.10.16 um 12:48 schrieb Adam Števko:
>>
>> Hi,
>>>
>>> On 12 Oct 2016, at 13:54, Marc Lobelle 
 wrote:

 On 11/10/16 18:19, Aurélien Larcher wrote:
> Hi,
> here is a short list of packages looking for adoption by a nice
> maintainer:
>
> benchmark/iozone
> developer/fakeroot
> developer/versioning/guilt
> editor/bvi
> editor/jedit
> image/virtualgl
> library/idnkit
> library/libosip2
> library/xmlrpc-c
> shell/shmux
> terminal/roxterm
> web/aget
>
> Considering that we have been talking about this for several months,
> if nobody is interested in updating them right now, I guess they
> should simply be deprecated instead of carrying old versions around.
>
> Aurélien
>
> Some old open source programs are not maintained any more but they do
 well what they are supposed to do. I think xfig is in this case. However
 they are still usefull and used. It is always a loss of time to have to
 find a source and recompile it when you install a new computer with a
 recent OS distribution (such as OI-Hipster1604).

 There are also programs that are still maintained but of which an old
 version is in OI, such as cups: it is better to have an old cups than no
 cups at all.

 As long as such programs work I would keep them in distributions. If
 one does not like to have them with the others, they could somehow be
 flagged as old.

 I'll see if I can make a package with a working version of xfig. Can
 you point me to an howto (assuming I have  a working compiled version for
 OI).

 Thanks

 Marc

>>> https://wiki.openindiana.org/oi/Building+with+oi-userland
>>>
>>> For packaging tips look for examples in other components. Also write
>>> down any problems with the quality of the documentation, so we can make it
>>> better.
>>>
>>> Cheers,
>>> Adam
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>> 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...
>> 2. How and when to update the build environment.
>> 3. A sample for a new package (steps that are needed) and a sample
>> for updating an existing package.
>> 4. Tips (collection of best practices and caveats).
>>
>> I think all this would make it easier for newcomers.
>>
>
> I need to update it but this is a start:
>
> https://openindiana.github.io/oi-docs/dev/userland/
>
> It is missing the recent addition of REQUIRED_PACKAGES and pre-publish.
>


Gh all the = where turned into # ...

http://hub.openindiana.ninja/?q=content/quick-start-oi-userland


>
> For simple packaging tasks and provided that the system is plain Hipster,
> installation in a zone is IMHO an unnecessary burden.
>
>
>
>>
>> Regards
>> Andreas
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

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

2016-10-12 Thread Aurélien Larcher 
On Wed, Oct 12, 2016 at 10:01 PM, Andreas Wacknitz 
wrote:

>
>
> Am 12.10.16 um 12:48 schrieb Adam Števko:
>
> Hi,
>>
>> On 12 Oct 2016, at 13:54, Marc Lobelle  wrote:
>>>
>>> On 11/10/16 18:19, Aurélien Larcher wrote:
 Hi,
 here is a short list of packages looking for adoption by a nice
 maintainer:

 benchmark/iozone
 developer/fakeroot
 developer/versioning/guilt
 editor/bvi
 editor/jedit
 image/virtualgl
 library/idnkit
 library/libosip2
 library/xmlrpc-c
 shell/shmux
 terminal/roxterm
 web/aget

 Considering that we have been talking about this for several months,
 if nobody is interested in updating them right now, I guess they
 should simply be deprecated instead of carrying old versions around.

 Aurélien

 Some old open source programs are not maintained any more but they do
>>> well what they are supposed to do. I think xfig is in this case. However
>>> they are still usefull and used. It is always a loss of time to have to
>>> find a source and recompile it when you install a new computer with a
>>> recent OS distribution (such as OI-Hipster1604).
>>>
>>> There are also programs that are still maintained but of which an old
>>> version is in OI, such as cups: it is better to have an old cups than no
>>> cups at all.
>>>
>>> As long as such programs work I would keep them in distributions. If one
>>> does not like to have them with the others, they could somehow be flagged
>>> as old.
>>>
>>> I'll see if I can make a package with a working version of xfig. Can you
>>> point me to an howto (assuming I have  a working compiled version for OI).
>>>
>>> Thanks
>>>
>>> Marc
>>>
>> https://wiki.openindiana.org/oi/Building+with+oi-userland
>>
>> For packaging tips look for examples in other components. Also write down
>> any problems with the quality of the documentation, so we can make it
>> better.
>>
>> Cheers,
>> Adam
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
> 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...
> 2. How and when to update the build environment.
> 3. A sample for a new package (steps that are needed) and a sample for
> updating an existing package.
> 4. Tips (collection of best practices and caveats).
>
> I think all this would make it easier for newcomers.
>

I need to update it but this is a start:

https://openindiana.github.io/oi-docs/dev/userland/

It is missing the recent addition of REQUIRED_PACKAGES and pre-publish.

For simple packaging tasks and provided that the system is plain Hipster,
installation in a zone is IMHO an unnecessary burden.



>
> Regards
> Andreas
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

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

2016-10-12 Thread Andreas Wacknitz 



Am 12.10.16 um 12:48 schrieb Adam Števko:

Hi,


On 12 Oct 2016, at 13:54, Marc Lobelle  wrote:


On 11/10/16 18:19, Aurélien Larcher wrote:
Hi,
here is a short list of packages looking for adoption by a nice maintainer:

benchmark/iozone
developer/fakeroot
developer/versioning/guilt
editor/bvi
editor/jedit
image/virtualgl
library/idnkit
library/libosip2
library/xmlrpc-c
shell/shmux
terminal/roxterm
web/aget

Considering that we have been talking about this for several months,
if nobody is interested in updating them right now, I guess they
should simply be deprecated instead of carrying old versions around.

Aurélien


Some old open source programs are not maintained any more but they do well what 
they are supposed to do. I think xfig is in this case. However they are still 
usefull and used. It is always a loss of time to have to find a source and 
recompile it when you install a new computer with a recent OS distribution 
(such as OI-Hipster1604).

There are also programs that are still maintained but of which an old version 
is in OI, such as cups: it is better to have an old cups than no cups at all.

As long as such programs work I would keep them in distributions. If one does 
not like to have them with the others, they could somehow be flagged as old.

I'll see if I can make a package with a working version of xfig. Can you point 
me to an howto (assuming I have  a working compiled version for OI).

Thanks

Marc

https://wiki.openindiana.org/oi/Building+with+oi-userland

For packaging tips look for examples in other components. Also write down any 
problems with the quality of the documentation, so we can make it better.

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

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...

2. How and when to update the build environment.
3. A sample for a new package (steps that are needed) and a sample 
for updating an existing package.

4. Tips (collection of best practices and caveats).

I think all this would make it easier for newcomers.

Regards
Andreas

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

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

2016-10-12 Thread Aurélien Larcher 
Update, Adam adopted idnkit:


> > benchmark/iozone
> > developer/fakeroot
> > developer/versioning/guilt
> > editor/bvi
> > editor/jedit(Franklin)
> > image/virtualgl
> > library/idnkit  (Adam)
> > library/libosip2
> > library/xmlrpc-c
> > shell/shmux (Predrag)
> > terminal/roxterm(Predrag)
> > web/aget(Franklin)
>
> xfig(Marc)
>

(Sorry for the flood, this is to avoid duplicate efforts)
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

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

2016-10-12 Thread Aurélien Larcher 
Update, four packages have found a maintainer:

> benchmark/iozone
> developer/fakeroot
> developer/versioning/guilt
> editor/bvi
> editor/jedit(Franklin)
> image/virtualgl
> library/idnkit
> library/libosip2
> library/xmlrpc-c
> shell/shmux (Predrag)
> terminal/roxterm(Predrag)
> web/aget(Franklin)

and xfig, of which I forgot the fmri, is taken care of by Marc.
Thank you

 Aurélien

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> ---
> Praise the Caffeine embeddings



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

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

2016-10-12 Thread Aurélien Larcher 
On Wed, Oct 12, 2016 at 1:54 PM, Marc Lobelle  wrote:
> On 11/10/16 18:19, Aurélien Larcher wrote:
>>
>> Hi,
>> here is a short list of packages looking for adoption by a nice
>> maintainer:
>>
>> benchmark/iozone
>> developer/fakeroot
>> developer/versioning/guilt
>> editor/bvi
>> editor/jedit
>> image/virtualgl
>> library/idnkit
>> library/libosip2
>> library/xmlrpc-c
>> shell/shmux
>> terminal/roxterm
>> web/aget
>>
>> Considering that we have been talking about this for several months,
>> if nobody is interested in updating them right now, I guess they
>> should simply be deprecated instead of carrying old versions around.
>>
>> Aurélien
>>
> Some old open source programs are not maintained any more but they do well
> what they are supposed to do. I think xfig is in this case. However they are
> still usefull and used. It is always a loss of time to have to find a source
> and recompile it when you install a new computer with a recent OS
> distribution (such as OI-Hipster1604).

Hi Marc,
thanks for your message, I agree with you.
We need to migrate them to oi-userland to be able to patch them and
rebuild them against dependencies if necessary.
I used xfig during my PhD so I'd be happy if you create a component for it.

>
> There are also programs that are still maintained but of which an old
> version is in OI, such as cups: it is better to have an old cups than no
> cups at all.
>
> As long as such programs work I would keep them in distributions. If one
> does not like to have them with the others, they could somehow be flagged as
> old.
>
> I'll see if I can make a package with a working version of xfig. Can you
> point me to an howto (assuming I have  a working compiled version for OI).

Additionally to Adam's link, this may help you:

https://openindiana.github.io/oi-docs/dev/userland/

Some Makefile examples are provided under 'templates' in oi-userland.
I should update the document to comply with recent guidelines.

Kind regards

Aurelien


>
> Thanks
>
> Marc
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss



-- 
---
Praise the Caffeine embeddings

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

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

2016-10-12 Thread Udo Grabowski (IMK) 

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

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

2016-10-12 Thread Udo Grabowski (IMK) 

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.
--
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

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

2016-10-12 Thread Adam Števko 
Hi,

> On 12 Oct 2016, at 13:54, Marc Lobelle  wrote:
> 
>> On 11/10/16 18:19, Aurélien Larcher wrote:
>> Hi,
>> here is a short list of packages looking for adoption by a nice maintainer:
>> 
>> benchmark/iozone
>> developer/fakeroot
>> developer/versioning/guilt
>> editor/bvi
>> editor/jedit
>> image/virtualgl
>> library/idnkit
>> library/libosip2
>> library/xmlrpc-c
>> shell/shmux
>> terminal/roxterm
>> web/aget
>> 
>> Considering that we have been talking about this for several months,
>> if nobody is interested in updating them right now, I guess they
>> should simply be deprecated instead of carrying old versions around.
>> 
>> Aurélien
>> 
> Some old open source programs are not maintained any more but they do well 
> what they are supposed to do. I think xfig is in this case. However they are 
> still usefull and used. It is always a loss of time to have to find a source 
> and recompile it when you install a new computer with a recent OS 
> distribution (such as OI-Hipster1604).
> 
> There are also programs that are still maintained but of which an old version 
> is in OI, such as cups: it is better to have an old cups than no cups at all.
> 
> As long as such programs work I would keep them in distributions. If one does 
> not like to have them with the others, they could somehow be flagged as old.
> 
> I'll see if I can make a package with a working version of xfig. Can you 
> point me to an howto (assuming I have  a working compiled version for OI).
> 
> Thanks
> 
> Marc

https://wiki.openindiana.org/oi/Building+with+oi-userland

For packaging tips look for examples in other components. Also write down any 
problems with the quality of the documentation, so we can make it better.

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

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

2016-10-12 Thread Marc Lobelle 

On 11/10/16 18:19, Aurélien Larcher wrote:

Hi,
here is a short list of packages looking for adoption by a nice maintainer:

benchmark/iozone
developer/fakeroot
developer/versioning/guilt
editor/bvi
editor/jedit
image/virtualgl
library/idnkit
library/libosip2
library/xmlrpc-c
shell/shmux
terminal/roxterm
web/aget

Considering that we have been talking about this for several months,
if nobody is interested in updating them right now, I guess they
should simply be deprecated instead of carrying old versions around.

Aurélien

Some old open source programs are not maintained any more but they do 
well what they are supposed to do. I think xfig is in this case. However 
they are still usefull and used. It is always a loss of time to have to 
find a source and recompile it when you install a new computer with a 
recent OS distribution (such as OI-Hipster1604).


There are also programs that are still maintained but of which an old 
version is in OI, such as cups: it is better to have an old cups than no 
cups at all.


As long as such programs work I would keep them in distributions. If one 
does not like to have them with the others, they could somehow be 
flagged as old.


I'll see if I can make a package with a working version of xfig. Can you 
point me to an howto (assuming I have  a working compiled version for OI).


Thanks

Marc

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