I'll echo Jim's comments in the SQLite case about calling everything
Volatile. It's really not appropriate, especially since these are
components that exist specifically for other projects to build on top of.
Given that these libraries are themselves built on top of the C versions of
the same libr
Laszlo (Laca) Peter wrote:
> A question for LSARC regarding these libs:
>
> Given that these are c++ libs, is it acceptable to ship
> duplicate copies built with g++ (/usr/sfw/bin/g++) and if
> so, where should they be installed?
>
> Why would that be useful? For building gtkmm-based
> applicati
John Fischer wrote:
> Instead, JDS in Nevada uses postrun for running these programs.
> Postrun generalizes the above idea by putting the complex
> script into a shared script (postrun itself) and using a
> single smf service for all first-boot commands.
When can consumers of postr
Nicolas Williams wrote:
> For OpenSSL the DLL hell considerations w.r.t. shipping multiple
> versions are serious enough, and DLL hell sufficiently likely, that it
> is reasonable that shipping multiple versions should give us pause. But
> even so, I tend to agree: just ship multiple versions.
Wh
Stefan Teleman wrote:
>
>
> James Carlson wrote:
>
>> The output of pkgconfig itself isn't private; it's used by other
>> software to find this library.
>>
>> The file that is contributed by this library to make pkgconfig work is
>> private. Nothing (other than pkgconfig itself) should be reach
John:
> Indicate Sun's involvement in the community
> [ ] Maintainer
> [ ] Contributor
> [ ] Monitoring
Rather than ask whether we are a contributor or a maintainer, we should
ask how the project is involved. Build fixes, code enhan
John Plocher wrote:
> Contract or not, since your team is putting it into Solaris, you
> are already committed to work with them to help avoid problems
> on the upgrade. Changing Committed to Contracted Volatile doesn't
> actually change the amount and type of work that you already are
> going to
Terrence:
> The libgc that is distributed with Sun Studio is a commercial product
> that was produced by Geodesic (which has gone out of business). We have
> the sources but no authorization to change or distribute them.
>
> I suspect that an implementation of a "Boehm-Demers-Weiser" GC being
>
Petr Sumbera wrote:
> James Carlson wrote:
>
>> Ah, I see. Still, when it comes time to do "tomcat6," it'll look a
>> little confusing to have "tomcat55" in there, so I'd prefer just "5."
>
> Ok, let's use "tomcat5".
We used to have just /usr/apache2 now we have /usr/apache2/2.2 and SMF
servic
James Carlson wrote:
>> /usr/lib/pkgconfig/lcms.pc Uncommitted Pkg-config Entry
>
> This actually looks Project Private to me.
The file location can be Project Private however the lcms name that is
implied by this can't be since that is what pkg-config(1) will use to
find it.
--
Gary Winiger wrote:
>>> As a future possible applicant for internship, I'm
>>> wondering if having access to those materials or tools will be
>>> necessary or if every thing I may need is going to be available in the
>>> forums and on OSo. I'm still trying to identify all of the
>>> responsibilit
Darren Reed wrote:
> James Carlson wrote:
>> ...
>>> Some other questions
>>> What is the rights profile for bridging?
>>>
>>
>> No new rights profile or change to existing profiles is needed. The
>> existing "Network Link Security" and "Network Management" rights
>> profiles include dlad
t was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080204/2c66daf0/attachment.html>
What about class action scripts that can't run in alternate boot / LU?
Does not providing a post-run mode for class action scripts mean that
postrun scripts will be more complicated than they have to be?
Brian,
See below.
John
Brian Cameron wrote:
>
> John:
>
>>>
>>> > Indicate Sun's involvement in the community
>>> > [ ] Maintainer
>>> > [ ] Contributor
>>> > [ ] Monitoring
>>>
>>> Rather than ask whether we are a contributor or a maintainer, we should
>>> ask how the
Forwarding to Laca.
Thanks,
John
Original Message
Subject: Re: PSARC/2008/078 - postrun - delayed execution environment
for procedural package scripts
Date: Mon, 04 Feb 2008 13:56:33 -0600
From: Nicolas Williams
To: John Fischer
CC: psarc-ext at sun.com
References: <47A75C4C
The libgc that is distributed with Sun Studio is a commercial product
that was produced by Geodesic (which has gone out of business). We have
the sources but no authorization to change or distribute them.
I suspect that an implementation of a "Boehm-Demers-Weiser" GC being
maintained by Hans Boe
> I agree that frequent updates to capture new formats
> are something we
> should strive for. Such a simple single source
> program could be a good
> test case to clear some crud out of the plumbing of
> Sun's processes and
> speed things up.
>
> But I'm not convinced frequent updates absolut
James:
I think the points raised in this case, that the SQLite community has
a good track record of interface stability is a good argument for
increasing its stability level.
That said, I have concerns with the suggestions that people are making
that *all* FOSS interfaces with the intent of stab
Brian Cameron wrote:
> If we are saying that SQLite has a great interface stability track
> record and such use cases, and therefore should not be Volatile, then
> this makes sense to me. However, if we are saying that all FOSS
> interfaces with an intent to be stable should be Uncommitted or high
After much discussion we have reached consensus that the original
proposal is satisfactory. We have received feedback on this alias,
other OpenSolaris forums, and private correspondence encouraging us to
provide this feature without additional restrictions. We will provide
documentation in th
Brian Cameron wrote:
>
> So, since then, our stance has been that interfaces should be
> Volatile unless there is a real use case that indicates users
> should require the interface.
>
So Joe OpenSolaris feels that inkscape would be a nice feature to add
to Solaris configure works, and the e
On Mon, Feb 04, 2008 at 04:57:17PM +, Darren J Moffat wrote:
> John Plocher wrote:
>
> > Contract or not, since your team is putting it into Solaris, you
> > are already committed to work with them to help avoid problems
> > on the upgrade. Changing Committed to Contracted Volatile doesn't
>
I'm sponsoring this fast-track for Magne Mahre. I believe this project
qualifies for a patch binding, but Magne can confirm whether or not he
intends to integrate this into Solaris 10 or earlier.
The timer is set for next Monday, February 11, 2008.
Danek
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080204/7bb12f7d/attachment.html>
and charset-unspecified text was scrubbed...
Name: proposal.txt
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080204/4d2d19e7/attachment.txt>
Darren J Moffat writes:
> Darren Reed wrote:
> > James Carlson wrote:
> >> ...
> >>> Some other questions
> >>> What is the rights profile for bridging?
> >>>
> >>
> >> No new rights profile or change to existing profiles is needed. The
> >> existing "Network Link Security" and "Network M
John Plocher wrote:
> Petr Sumbera wrote:
>> James Carlson wrote:
http://tomcat.apache.org/connectors-doc/generic_howto/workers.html
>>> OK; so matching all of this up is "merely" a user configuration
>>> problem, right?
>>
>> Yes.
>
> This seems to be a huge architectural hole - things can't
I wanted to update the case relative to the meeting I had with the case
owner, submitter, and other's of the ON power management team after
PSARC 30 Jan.
As an aside, I'll not be present at 6 Feb PSARC and will be in and out
on personal business the next couple weeks.
Sorry for the length. I'm tr
John Plocher wrote:
> Petr Sumbera wrote:
>> John Plocher wrote:
>>> Petr Sumbera wrote:
Tomcat is started (beside manually) via Apache 1.3 init script
>>>
>>> What about Apache 2.x - how does this work with that version?
>>
>> Answer is simple. It doesn't work.
>
> OK, but...
>
>>
>> Tomca
Irene Huang writes:
> There are many projects that use gc, including
[...]
> /usr/lib/libcord.so Volatilelibrary
> /usr/lib/libgc.so Volatilelibrary
> /usr/include/gc/*.h Volatileheader files
>
James Carlson wrote:
> Gary Winiger writes:
>
>>> This case was closed approved in last PSARC meeting.
>>>
>>> Material was updated and saved as 'spec.txt' in case directory. In the
>>> updated material, interface name '/dev/dsp' was changed to
>>> '/dev/private_dsp' so that users won't stumbl
Gary Winiger writes:
> > This case was closed approved in last PSARC meeting.
> >
> > Material was updated and saved as 'spec.txt' in case directory. In the
> > updated material, interface name '/dev/dsp' was changed to
> > '/dev/private_dsp' so that users won't stumble into it purely by
>
Brian Cameron writes:
> James:
> > It doesn't happen for Solaris itself, and expecting that out of
> > someone else doesn't seem right to me.
>
> The JDS team currently does ABI comparison for all of our Committed
> interfaces.
Good to hear.
> > You don't need to promise to boil away the ocean t
> > Did I completely miss the committee's thrust?
>
> We agreed that as long as it was kept reasonably out of harm's way
> until the stability is firmed up, we didn't much care how that was
> done.
>
> I had assumed that meant "private_dsp," as Garrett said during ARC
> business that he wasn
Irene Huang wrote:
>
>> I am setting the timeout for this case to be Feb 13th.
>> Please review the proposal at
>> http://sac.eng/Archives/CaseLog/arc/LSARC/2008/068/proposal.txt
I have no particular objection to this case, because there a bunch of
FOSS that wants to use it. But, assuming India
36 matches
Mail list logo
