Re: [oi-dev] Feature #1738 add Asterisk package to oi-build
Cleanup is here. Hopefully ready for triage now. https://bitbucket.org/cellis_oidev/oi-build/changeset/35222c592a5f On Sat, Nov 12, 2011 at 3:26 AM, Josef 'Jeff' Sipek jef...@josefsipek.netwrote: On Mon, Nov 07, 2011 at 04:50:32PM +, Colin Ellis wrote: https://bitbucket.org/cellis_oidev/oi-build/changeset/755748bc74a3 Did you get the Makefile from Oracle? It has an oracle copyright. If not, you should also use the Illumos version of the CDDL header. Speaking of which, is your name Random Developer? ;) You might want to fix up the manifest. Something tells me that all the files in /etc should get mangled to make sure pkg doesn't blow them away. Perhaps something like what irssi has: transform file path=etc/irssi.conf - default preserve true transform file path=etc/irssi.conf - default mode 0644 Jeff. -- We have joy, we have fun, we have Linux on a Sun... ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] pkg version bump in /dev
A bunch of people have been using /experimental's pkg. Everything seems to work quite well. (For those of you who don't know, /experimental has the 173 pkg backport.) Thoughts about moving this into /dev? I think it'll make things easier for us in the long run - less divergence between /dev and /experimental, as well as very useful features such as mediated links. Jeff. -- Bad pun of the week: The formula 1 control computer suffered from a race condition ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] pkg version bump in /dev
The changes of Yuri's to illumos's pkg build, recently, should make this no longer harmful to us. It'd be nice if someone could confirm that though. -- Rich ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] pkg version bump in /dev
On Wed, Nov 23, 2011 at 06:41:22PM -0500, Richard Lowe wrote: The changes of Yuri's to illumos's pkg build, recently, should make this no longer harmful to us. It'd be nice if someone could confirm that though. How does one test it? Just compile the gate? Jeff. -- Once you have their hardware. Never give it back. (The First Rule of Hardware Acquisition) ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Feature #1738 add Asterisk package to oi-build
On Wed, Nov 23, 2011 at 09:54:04PM +, Colin Ellis wrote: Cleanup is here. Hopefully ready for triage now. https://bitbucket.org/cellis_oidev/oi-build/changeset/35222c592a5f Out of curiosity, what's all the .cleancount about? You ended up with mangled/* in the p5m. Other than that, it looks good. Jeff. -- C is quirky, flawed, and an enormous success. - Dennis M. Ritchie. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Feature #1744 add ruby 1.9.3 to oi-build
On Sun, Nov 20, 2011 at 11:45:28AM +, Colin Ellis wrote: I'm tidying up the files as requested. I've run a make test, which passes. I haven't found any DTrace patches for the 1.9 series of ruby. The SFE build of 1.9.0 doesn't have any applied. I'd suggest having two ruby packages in the repo: ruby19 with latest code and ruby18 with dtrace. Well, it feels like a regression to have a newer version without DTrace support. Or did I miss the memo and DTrace got mainlined? Agreed on the nitpicks that Alasdair pointed out. Jeff. -- UNIX is user-friendly ... it's just selective about who its friends are ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Feature 1768 - add dovecot to oi-build
On Sun, Nov 20, 2011 at 11:34:53AM +, Colin Ellis wrote: hopefully this is everything https://bitbucket.org/cellis_oidev/oi-build/changeset/856e6772091a LGTM On Sat, Nov 19, 2011 at 10:36 PM, Alasdair Lumsden alasdai...@gmail.comwrote: Forgot to mention, your .p5m files need the opensolaris package classifications being filled in. If you're not sure what to use, just shout and we can collectively think up an answer. On 11/19/11 10:00 PM, Colin Ellis wrote: https://bitbucket.org/cellis_**oidev/oi-build/changeset/**d7b944645d37https://bitbucket.org/cellis_oidev/oi-build/changeset/d7b944645d37 On Tue, Nov 15, 2011 at 12:43 AM, Josef 'Jeff' Sipek jef...@josefsipek.net mailto:jef...@josefsipek.net** wrote: On Sat, Nov 12, 2011 at 11:17:10PM +, Colin Ellis wrote: bitbucket here: https://bitbucket.org/cellis_**oidev/oi-build/changeset/** d7c2addf18b7https://bitbucket.org/cellis_oidev/oi-build/changeset/d7c2addf18b7 Awesome, this one was on my todo list. Less work for me :) 1) no need to set --prefix --sbindir yourself 2) $(ETCDIR) instead of /etc 3) did the `gmake publish` not complain about the missing info.classification? 4) Do we really need to ship all those .a and .la files? Solaris likes shared libs a lot - and handles them pretty well too. 5) Do the files in usr/share/doc have the doc facet? (They should; you can check the published manifest.) 6) Is there an SMF manifest? Thanks! Jeff. -- All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can’t get them together again, there must be a reason. By all means, do not use a hammer. — IBM Manual, 1925 __**_ oi-dev mailing list oi-dev@openindiana.org mailto:oi-dev@openindiana.org** http://openindiana.org/**mailman/listinfo/oi-devhttp://openindiana.org/mailman/listinfo/oi-dev __**_ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/**mailman/listinfo/oi-devhttp://openindiana.org/mailman/listinfo/oi-dev __**_ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/**mailman/listinfo/oi-devhttp://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev -- Once you have their hardware. Never give it back. (The First Rule of Hardware Acquisition) ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] gcc default
After figuring out the sfe repository stuff, we finally managed to install gcc-4. OpenIndiana runs nicely in 64bit, and everything is 64bit, including perl and perl modules. And yet, when you use gcc, the default output is 32bit. Does this really make sense any more? (on intel at least). Sure I can add -m64 to everything I compile, (presumably including perl modules) but is there no easy way to change the default from -m32 to -m64 ? I was stuffing around in the /usr/gcc/4.6/lib/gcc/i386-pc-solaris2.11/4.6.2/plugin/include/config/i386 area, but it appears to be used when compiling gcc. Not after. Should the default be changed to 64bit in the repository? Lund -- Jorgen Lundman | lund...@lundman.net Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo| +81 (0)90-5578-8500 (cell) Japan| +81 (0)3 -3375-1767 (home) ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
