root@silver:~# pkg contents -rm osnet-incorporation |grep git-rev |grep
illumos
set name=illumos-gate.info.git-rev
value=da2c0e64794ff584dca660fcc94a444dcc0d6c0b
root@silver:~#
Now we have it. I am update OI to test the improvement in dmake.
On Mon, Nov 16, 2015 at 6:46 PM, Jim Klimov wrote:
>
On 11/16/15 12:16 AM, Stefan Müller-Wilken wrote:
As for contributing packages, I think it would help to have a full tutorial
starting wirh preparing a packaging zone, downloading a tgz package from a
source repository (e. g. latest tomcat) over creating IPS metadata to packaging
and lastly de
Well, and the natural 'somewhere' for that topic could be OI wiki, I guess. :-)
Only question that comes to mind is, if it wouldn't be better to start with
/dev (or /hipster for that matter) themselfs? Because that's where the most
recent Tomcat is 6.0.37, the latest httpd is 2.2.26, the most up
in the meantime, you can start immediatly setting
up an SFE environment, if you can read Japanese.
https://pt.osdn.jp/projects/jposug/wiki/howtouse
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mai
Thomas Wagner writes:
> If at least two people raise hands, I'll put up a draft page
> somewhere which describes the usage of the boostrap-sfe-*
> script. Then the build-recipes form the SFE repository can be built
> locally.
I think this is a good idea.
Regards -- Volker
--
---
On Sun, Nov 15, 2015 at 11:16:00PM +, Stefan M??ller-Wilken wrote:
>
> Full 'thumbs up' to all you've said. I admit that I've treated SFE as part of
> the core. My bad, I'll fix that following your suggestions and report.
thanks :)
> Regarding maintaining and supporting OI, I know what yo
In regard to: Re: [OpenIndiana-discuss] Hipster upgrade problem, Stefan...:
As for contributing packages, I think it would help to have a full
tutorial starting wirh preparing a packaging zone, downloading a tgz
package from a source repository (e. g. latest tomcat) over creating IPS
metadata to
16 ноября 2015 г. 12:29:41 CET, Mohamed Khalfella пишет:
>Hi,
>
>I can see 6455 is in illumos-gate now. When it is expected to be able
>to
>pull the modified dmake bits from OI repository.
AFAIK Hipster is continuously built by Jenkins jobs which regularly poll their
respective repositories, so
Thanks for your reply,
7c0fa7e5c69bad99deb669aa7703bfa15bb58d5e is one commit
before da2c0e64794ff584dca660fcc94a444dcc0d6c0b. May be I have to wait till
tomorrow
On Mon, Nov 16, 2015 at 4:38 PM, Alexander Pyhalov wrote:
> On 11/16/2015 14:29, Mohamed Khalfella wrote:
>
>> Hi,
>>
>> I can see 6
On 11/16/15 12:02 PM, Stefan Müller-Wilken wrote:
Hmmm... so the better approach for Internet facing nodes is to move on to
/hipster but be defensive in your update policy? Because with what you say and
in contrast to Udo, I'd rather call /dev than /hipster going nowhere as more
and more /dev
Hi,
I can see 6455 is in illumos-gate now. When it is expected to be able to
pull the modified dmake bits from OI repository.
--
BR,
Mohamed A. Khalfella
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/ma
Hmmm... so the better approach for Internet facing nodes is to move on to
/hipster but be defensive in your update policy? Because with what you say and
in contrast to Udo, I'd rather call /dev than /hipster going nowhere as more
and more /dev packages have reached EOL in their respective projec
On 16 November 2015 at 08:55, Stefan Müller-Wilken <
stefan.mueller-wil...@acando.de> wrote:
> What I'm feeling quite uneasy with is the fact that we now have two
> distributions: hipster that gets more recent software packages & security
> fixes and dev that is said to be the more (or only?) stab
What I'm feeling quite uneasy with is the fact that we now have two
distributions: hipster that gets more recent software packages & security fixes
and dev that is said to be the more (or only?) stable choice. Or in other
words: choose stability _OR_ security - a no-win-situation.
How can we ge
14 matches
Mail list logo
