I followed below link to set up my SXCE 112_snv x86 so that I can install apps
from blastwave.org.
http://www.blastwave.org/howto.html
However, forexample if I install nmap (or any other package),
I noticed that pkgutil intend to install other dependencies that they already
installed in my machin
it's normal.
blastwave "duplicates" many things
FYI: nmap *is* in SXCE
On Sun, May 3, 2009 at 12:37 PM, vuthecuong wrote:
> I followed below link to set up my SXCE 112_snv x86 so that I can install
> apps from blastwave.org.
> http://www.blastwave.org/howto.html
> However, forexample if I instal
vuthecuong wrote:
> I followed below link to set up my SXCE 112_snv x86 so that I can install
> apps from blastwave.org.
> http://www.blastwave.org/howto.html
> However, forexample if I install nmap (or any other package),
> I noticed that pkgutil intend to install other dependencies that they a
Andras Barna wrote:
> it's normal.
> blastwave "duplicates" many things
Blastwave does not "duplicate" things but does what it needs to do.
If Solaris did inlcude more OSS with Solaris 8, things would look different.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13
On Sun, May 3, 2009 at 12:23 PM, Joerg Schilling
wrote:
> Andras Barna wrote:
>
>> it's normal.
>> blastwave "duplicates" many things
>
> Blastwave does not "duplicate" things but does what it needs to do.
>
> If Solaris did inlcude more OSS with Solaris 8, things would look different.
Hi, I b
vuthecuong wrote:
I noticed that pkgutil intend to install other dependencies that they already
installed in my machine:
===
bash-3.2# /opt/csw/bin/pkgutil --install nmap
Checking catalog integrity with gpg.
gpg: 2009年05月01日 10時56分49秒 ICTにDSA鍵ID A1999E90で施された署名
gpg: “Blas
On Sun, May 3, 2009 at 5:48 PM, Oscar del Rio wrote:
> vuthecuong wrote:
>>
>> I noticed that pkgutil intend to install other dependencies that they
>> already installed in my machine:
>> ===
>> bash-3.2# /opt/csw/bin/pkgutil --install nmap
>> Checking catalog integrity wit
Joerg Schilling wrote:
> For any of the dependencies, it should be obvious that the dependencies that
> are valid for Solaris 8 need to be installed for Solaris 11 too as any
> blastwave package need to use the other probrams from it's own environment in
> order to behave reliably.
It can also r
Martin Bochnig wrote:
Hi, I believe he means, that the dependency resolution algorithm used
by csw (in the past with pkg-get, and also now) is suboptimal (which
is not a shame, as most others are, too).
For example, speaking in directed graph language (#0), Blastwave
doesn't ensure that cycles ar
On Mon, May 4, 2009 at 5:15 AM, Shawn Walker wrote:
> Martin Bochnig wrote:
>>
>> Hi, I believe he means, that the dependency resolution algorithm used
>> by csw (in the past with pkg-get, and also now) is suboptimal (which
>> is not a shame, as most others are, too).
>> For example, speaking in d
Martin Bochnig wrote:
On Mon, May 4, 2009 at 5:15 AM, Shawn Walker wrote:
blastwave's packages are built with the assumption that libaries live
relative to the rest of the programs (such as under /opt/csw), are compiled
with different flags, and generally assume dependencies must be provided by
Shawn Walker wrote:
> My point was that a dependency algorithm was not the cause of the issue
> with the blastwave packages. It is primarily an issue of how they are
> built.
There is no "issue" with Blastwave packages. These packages just make use from
the binary compatibility grant from Su
Joerg Schilling wrote:
Shawn Walker wrote:
My point was that a dependency algorithm was not the cause of the issue
with the blastwave packages. It is primarily an issue of how they are
built.
There is no "issue" with Blastwave packages. These packages just make use from
the binary compati
Shawn Walker wrote:
> Joerg Schilling wrote:
> > Shawn Walker wrote:
> >
> >> My point was that a dependency algorithm was not the cause of the issue
> >> with the blastwave packages. It is primarily an issue of how they are
> >> built.
> >
> > There is no "issue" with Blastwave packages. T
On Mon, May 4, 2009 at 11:28 AM, Martin Bochnig wrote:
> That's not the problem.
> The problem is, that 5.9, 5.10, 5.10.1 and 5.11 are only symlinks to
> 5.8 most of the time, inside the csw repo.
> For simplicity it would have been sufficient to concentrate only on 2
> build targets, out of the c
On Mon, May 4, 2009 at 10:57 AM, Joerg Schilling
wrote:
> Shawn Walker wrote:
>
>> Joerg Schilling wrote:
>> > Shawn Walker wrote:
>> >
>> >> My point was that a dependency algorithm was not the cause of the issue
>> >> with the blastwave packages. It is primarily an issue of how they are
>> >>
Alan Coopersmith wrote:
> Joerg Schilling wrote:
> > For any of the dependencies, it should be obvious that the dependencies that
> > are valid for Solaris 8 need to be installed for Solaris 11 too as any
> > blastwave package need to use the other probrams from it's own environment
> > in
> >
Martin Bochnig wrote:
> In 2005 I got banned from the csw mailing lists (because I didn't like
> Dennis' ***intransparent*** ***business model*** , where all work
I have no idea why you don't like Dennis
...
> And: During times of non-dictatorship COMMUNITY effort, under
> co-leadersh
On Mon, May 4, 2009 at 5:23 PM, Joerg Schilling
wrote:
> Alan Coopersmith wrote:
>
>> Joerg Schilling wrote:
>> > For any of the dependencies, it should be obvious that the dependencies
>> > that
>> > are valid for Solaris 8 need to be installed for Solaris 11 too as any
>> > blastwave package n
I have reasons.
What I didn't like were a few questions of how things were handled.
Nevertheless, I do respect him.
It is a thing of the past, it is ok.
%martin
On Mon, May 4, 2009 at 5:44 PM, Joerg Schilling
wrote:
> Martin Bochnig wrote:
>
>> In 2005 I got banned from the csw mailing lists
Joerg Schilling wrote:
> But please note that at the time Solaris 8 was created, Sun was just in a
> state
> where the managers believed in closed source. With Solaris 8, there are only
> thre OSS packages:
>
> - mkisofs
> - gzip
> - bash
Even Solaris 8 had a lot more than just 3 o
On Mon, May 4, 2009 at 8:22 PM, Alan Coopersmith
wrote:
> Joerg Schilling wrote:
>> But please note that at the time Solaris 8 was created, Sun was just in a
>> state
>> where the managers believed in closed source. With Solaris 8, there are only
>> thre OSS packages:
>>
>> - mkisofs
>> -
Alan Coopersmith wrote:
> Joerg Schilling wrote:
> > But please note that at the time Solaris 8 was created, Sun was just in a
> > state
> > where the managers believed in closed source. With Solaris 8, there are
> > only
> > thre OSS packages:
> >
> > - mkisofs
> > - gzip
> > - bash
>
>You are correct for perl and tcsh but for the rest you are mistaken.
>
>Even though, Sun did plan to use the OSS version of sendmail in 1992, this did
>not happen before OpenSolaris was released.
Long before; I'm sure John Beck can tell you exactly when we started to
use a more modern sendmai
casper@sun.com wrote:
> >You are correct for perl and tcsh but for the rest you are mistaken.
> >
> >Even though, Sun did plan to use the OSS version of sendmail in 1992, this
> >did
> >not happen before OpenSolaris was released.
>
>
> Long before; I'm sure John Beck can tell you exactly when
Maybe the new pkg system will slowly take over from blastwave and maybe it
won't, but as long as blastwave is the only source for software like DVD
players it will still be needed.
--
This message posted from opensolaris.org
___
opensolaris-discuss mai
i dont think that you need the whole bunch of blastwave to be able to
play a DVD..
On Tue, May 5, 2009 at 2:01 PM, Charles Hedrick wrote:
> Maybe the new pkg system will slowly take over from blastwave and maybe it
> won't, but as long as blastwave is the only source for software like DVD
> pla
27 matches
Mail list logo
