Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
On 12/20/2012 04:35 PM, Andrey N. Oktyabrski wrote: On 12/20/2012 03:57 PM, Volker A. Brandt wrote: Andrey N. Oktyabrski wrote: $ cat /usr/pkgsrc/pkgtools/gensolpkg/DESCR This is a small utility to translate from NetBSD-derived pkgsrc packages into Solaris packages. Yes, that was what I was thinking of. I had tried it years ago and it looked nice. Thanks for writing it! No-no-no - these thanks not for me :-) I'm not an author. I think, the author is agc@ Hmm... It seems misc/epm is more "right" tool: $ cat /usr/pkgsrc/misc/epm/DESCR EPM is an open source UNIX software and file packaging program that generates distribution archives from a list of files. EPM provides a complete, cross-platform software distribution solution for your applications. ESP generates both native and "portable" script-based distribution packages complete with installation and removal scripts and standard install/uninstall GUIs. The installers can be customized with product logos, "readme" files, and click-wrap licenses as desired. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
On 12/20/2012 03:57 PM, Volker A. Brandt wrote: Andrey N. Oktyabrski wrote: $ cat /usr/pkgsrc/pkgtools/gensolpkg/DESCR This is a small utility to translate from NetBSD-derived pkgsrc packages into Solaris packages. Yes, that was what I was thinking of. I had tried it years ago and it looked nice. Thanks for writing it! No-no-no - these thanks not for me :-) I'm not an author. I think, the author is agc@ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
Hi, But what about using pkgbuild from the spec file extra (SFE) team which is available from the OI-SFE repository ? You can build you packages and publish them to your own local IPS repository in no time. You actually don't need to learn how to make IPS packages, just write spec files like for RPM. Moreover pkgbuild supports generation of SVR4 packages. While I don't understand why people should hate IPS, what I see indeed as you point it, is lack of simple "reproductible steps" tutorials written by users and lack of commitment around one way to provides packages. If you just want IPS packages to be built from source I cannot see why you would try to find another solution than the one used to build the OI repositories: it's straightforward and a build zone can be set up quickly. I started writing short tutorials for a bundle of spec files for scientific software I want to contribute to SFE here http://forge.distrans.org/projects/oi-sci/wiki It's not elaborate yet but anyone willing to contribute is welcome. Or if you can identify missing piece of information I am willing to fill the blanks. Best regards, a On Thu, Dec 20, 2012 at 6:23 AM, Dormition Skete wrote: > Well, ideally, if every one of us who needed to install a piece of > software that wasn't available in package form would make and sponsor an > IPS package for it, I think that would be the best thing. But I, for one, > am not real keen on learning how to make IPS packages -- especially since > so many people hate IPS, and in my opinion, its future looks questionable. > > What you are proposing sounds interesting, but again, it's yet another > thing to learn, and another layer of complexity which also duplicates that > which the packaging system should take care of. > > For most (?) of us, we build a server once or twice a year. Some things > are just not worth the trouble to automate. > > My own rule of thumb is, every program I write has to pay for itself -- > with money and/or time saved -- within the first year. If it doesn't do > that, I don't bother with it. > > > > On Dec 19, 2012, at 9:55 PM, Jason Matthews wrote: > > > > > > > > >> Perhaps some of you all might like to contribute to it, too? > > > > This is an interesting topic. > > > > I am also fond of reproducible processes. I learned from a colleague long > > ago to write Makefiles which in turn run other make files to boot strap > an > > entire software stack -- sort of a lord of the rings, one ring to rule > them > > all sort of setup. I was introduced to this concept about twelve years > ago > > and I have been using it ever since. > > > > I haven't bridged the gap between my "/usr/local" build and pkg formatted > > packages but I can't help but wonder if it is better to supply an > automated > > build system rather than manual instructions -- any automated build > system > > that worked would be preferable to doing something manually. > > > > A few years ago I thought about releasing the whole thing in a VirtualBox > > image because then it is fully plug and play but never got around to it. > One > > down side is the image would be rather large to accommodate the large > number > > of packages now included in my build system. > > > > I am not poopooing your idea in any way. I am just wondering if we can > take > > it up a level or two. > > > > j. > > ___ > > OpenIndiana-discuss mailing list > > OpenIndiana-discuss@openindiana.org > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- LARCHER Aurélien| KTH, School of Computer Science and Communication Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 5 Mob.: +46 (0) 7 09 46 40 17 | 100 44 Stockholm, SWEDEN --- Praise the Caffeine embeddings ... ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
Andrey N. Oktyabrski wrote: > $ cat /usr/pkgsrc/pkgtools/gensolpkg/DESCR This is a small utility > to translate from NetBSD-derived pkgsrc packages into Solaris > packages. Yes, that was what I was thinking of. I had tried it years ago and it looked nice. Thanks for writing it! Regards -- Volker -- Volker A. Brandt Consulting and Support for Oracle Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt "When logic and proportion have fallen sloppy dead" ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
On 12/20/2012 01:02 PM, Volker A. Brandt wrote: However, it is another step away from "real" Solaris. The "old" Solaris up to 10 has SVR4, the "new" Solaris has IPS. So these are really the only options for any distro targeted for the "mainstream" users. $ cat /usr/pkgsrc/pkgtools/gensolpkg/DESCR This is a small utility to translate from NetBSD-derived pkgsrc packages into Solaris packages. I wrote this as an aid to understanding Solaris packages, and to provide some Solaris packages which can be used in jumpstart, and manipulated with the Solaris package manipulation tools, but still have the benefit of the original package being maintained by a number of people who know what they're doing, and put a lot of time into keeping abreast of latest versions and bug fix releases. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
Mads Worsøe Duun writes: > Why not look at pkgsrc? It is working well on Openindiana/Illumos Yes, pkgsrc is a great tool. To install some software with pkgsrc and watch it pull down the source, compile, install, etc. is really amazing. However, it is another step away from "real" Solaris. The "old" Solaris up to 10 has SVR4, the "new" Solaris has IPS. So these are really the only options for any distro targeted for the "mainstream" users. That pkgsrc can work well for a specialized distro like SmartOS is absolutely true. There are also mods to make pkgsrc produce SVR4 pkgs somewhere. Maybe pkgsrc can be extended to produce IPS pkgs as well... Regards -- Volker -- Volker A. Brandt Consulting and Support for Oracle Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt "When logic and proportion have fallen sloppy dead" ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
Why not look at pkgsrc? It is working well on Openindiana/Illumos, and is supported by Joyent ( http://www.perkin.org.uk/posts/pkgsrc-2012Q3-packages-for-illumos.html). Joyent even adapt the packages to support SMF on SmartOS. Mads Worsøe Duun ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
Sorry. I'll go to the OpenCSW group if I find I need their packages. OpenIndiana didn't seem to be listed on their website as something they support. And after three weeks of my first OI install, I probably wasn't thinking very clearly. System admin stuff isn't an area I'm very strong in. Have a nice night! On Dec 20, 2012, at 1:00 AM, solarg wrote: > On 12/20/12 06:59, dormitionsk...@hotmail.com wrote: >> How did you get OpenCSW to work in OpenIndiana? >> >> I tried it, and couldn't get the repository to load. When I did "pkgadd >> -dhttp://get.opencsw.org/now";, it errored out. Trying to add it via the gui >> didn't fare any better. I didn't feel like going onto their newsgroup for >> assistance, so I just installed from source. >> > > i can't help if you just say "it errored out" sorry > pkgadd works fine for me. And i don't understand the difference between going > to the "opencsw" newsgroup or OI, it's just a newsgroup, isnt it? > i was just talking about sharing experience, and it's just my point of view. > I prefer to join an existing group instead of starting from scratch. But > that's just my point of view > > gerard > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
On 12/20/12 06:59, dormitionsk...@hotmail.com wrote: How did you get OpenCSW to work in OpenIndiana? I tried it, and couldn't get the repository to load. When I did "pkgadd -dhttp://get.opencsw.org/now";, it errored out. Trying to add it via the gui didn't fare any better. I didn't feel like going onto their newsgroup for assistance, so I just installed from source. i can't help if you just say "it errored out" sorry pkgadd works fine for me. And i don't understand the difference between going to the "opencsw" newsgroup or OI, it's just a newsgroup, isnt it? i was just talking about sharing experience, and it's just my point of view. I prefer to join an existing group instead of starting from scratch. But that's just my point of view gerard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
How did you get OpenCSW to work in OpenIndiana? I tried it, and couldn't get the repository to load. When I did "pkgadd -d http://get.opencsw.org/now";, it errored out. Trying to add it via the gui didn't fare any better. I didn't feel like going onto their newsgroup for assistance, so I just installed from source. By the time I learned about them, I think I was almost done installing stuff on our server. Same thing with Sunfreeware. On Dec 19, 2012, at 10:43 PM, solarg wrote: > hello, > why don't join the OpenCSW project? ok they're actullay focused on Solaris > 10, but i used their packages on S11 and OI, and they're very reactive and > experienced with compilation process. > I know they want to create an IPS repository. > For instance, if i need a tool like Request Tracker, i can't imagine that i > have to compile all the perl modules myself. > > gerard > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
hello, why don't join the OpenCSW project? ok they're actullay focused on Solaris 10, but i used their packages on S11 and OI, and they're very reactive and experienced with compilation process. I know they want to create an IPS repository. For instance, if i need a tool like Request Tracker, i can't imagine that i have to compile all the perl modules myself. gerard ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
Well, ideally, if every one of us who needed to install a piece of software that wasn't available in package form would make and sponsor an IPS package for it, I think that would be the best thing. But I, for one, am not real keen on learning how to make IPS packages -- especially since so many people hate IPS, and in my opinion, its future looks questionable. What you are proposing sounds interesting, but again, it's yet another thing to learn, and another layer of complexity which also duplicates that which the packaging system should take care of. For most (?) of us, we build a server once or twice a year. Some things are just not worth the trouble to automate. My own rule of thumb is, every program I write has to pay for itself -- with money and/or time saved -- within the first year. If it doesn't do that, I don't bother with it. On Dec 19, 2012, at 9:55 PM, Jason Matthews wrote: > > > >> Perhaps some of you all might like to contribute to it, too? > > This is an interesting topic. > > I am also fond of reproducible processes. I learned from a colleague long > ago to write Makefiles which in turn run other make files to boot strap an > entire software stack -- sort of a lord of the rings, one ring to rule them > all sort of setup. I was introduced to this concept about twelve years ago > and I have been using it ever since. > > I haven't bridged the gap between my "/usr/local" build and pkg formatted > packages but I can't help but wonder if it is better to supply an automated > build system rather than manual instructions -- any automated build system > that worked would be preferable to doing something manually. > > A few years ago I thought about releasing the whole thing in a VirtualBox > image because then it is fully plug and play but never got around to it. One > down side is the image would be rather large to accommodate the large number > of packages now included in my build system. > > I am not poopooing your idea in any way. I am just wondering if we can take > it up a level or two. > > j. > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Knowledge Base for Compiling and InstallingSoftware Not Available as Packages.
> Perhaps some of you all might like to contribute to it, too? This is an interesting topic. I am also fond of reproducible processes. I learned from a colleague long ago to write Makefiles which in turn run other make files to boot strap an entire software stack -- sort of a lord of the rings, one ring to rule them all sort of setup. I was introduced to this concept about twelve years ago and I have been using it ever since. I haven't bridged the gap between my "/usr/local" build and pkg formatted packages but I can't help but wonder if it is better to supply an automated build system rather than manual instructions -- any automated build system that worked would be preferable to doing something manually. A few years ago I thought about releasing the whole thing in a VirtualBox image because then it is fully plug and play but never got around to it. One down side is the image would be rather large to accommodate the large number of packages now included in my build system. I am not poopooing your idea in any way. I am just wondering if we can take it up a level or two. j. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
