Sriram Natarajan wrote:
>
> I do agree that this has lot of shortcomings like - unable to bind at
> port 80 by default etc.
Don't forget to also assign PRIV_NET_PRIVADDR, which solves that.
(With the upcoming fine grained authorizations we'll be able to grant
privilege to port 80 alone, even be
Thava Alagu wrote:
>
>I propose to deliver this into new config dir say,
> /etc/apache2/2.2/webapp.d
That's a fairly major proposal, I'm not sure I see why a new dir is
needed? What are the precise usage semantics of this?
I'd say if you deliver an apache-specific glue package (as you seem t
Thava Alagu wrote:
>
> As I understand dependency does not serve any purpose other than
>usability -- for users
>to easily discover dependencies and get the software up and running.
>So, too obvious dependencies may be omitted. For example, a package
>may not
>specify (dir
Thava Alagu wrote:
>
> OK, if that is preferable, I will go with SUNWphppgadmin-main
Very much not preferable. While your source will still build SysV
packages in the transition period, keep in mind the final package name
you'll want users to be able to access via IPS.
> I don't think these
Bjorn Munch wrote:
>
> - Package names: instead of "u" and "r" suffixes, current policy
>recommends "-config" for the package with files under /etc.
Not that I know of.. in fact I see there is only one package with
such naming (SUNWpgbouncer-pg83-config).
But no matter really, since the wh
> Thanks. Creating a link to libsqlite3-3.5.4.so.0 worked. Just not sure
> why it was not already there.
Would it be possible for you to check if libsqlite3.so.0 exists before
the Vermillion 91 build installation ?
-- Seema.
