From: David Combs on
In article <hgeg5n$2qd$1(a)reader1.panix.com>,
Cydrome Leader <presence(a)MUNGEpanix.com> wrote:
>David Combs <dkcombs(a)panix.com> wrote:
....
....

>
>It's two steps of keeping the job. One is keeping busy and two is not
>using bogus software from some site that went away after people started to
>fight over a domain name.
>
>It's nonense like that that makes management really question the usage of
>"free" software in a business environment, which is too bad as quite a bit
>of it is really good stuff.
>
>I can't imagine telling anybody that "sorry, I can't make that app server
>because I can't find the installers for the version of [whatever package]
>we used last time, let's just try some other random version and hope it
>behaves 100% the same as the existing systems we're running".

Yes, seems too bad that when the split happened,
the two of them couldn't work out a scheme
where the Solaris user could grab stuff from
either site. With the indended beneficiary actually
losing benefit: before the split-up, user would
get the benefit of let's call it 2x people's efforts,

whereas after the split, a user can benefit
from the gladly-performed work of x people -- user
has to choose ONE of the teams, and stick with
that. Period!

That's my take of the situation, anyway.

David




From: David Combs on
In article <29fc6a86-d97a-4269-ba2e-b233d3d598f0(a)r24g2000prf.googlegroups.com>,
phil.googlenews(a)bolthole.com <phil.googlenews(a)bolthole.com> wrote:
>BTW, let's get some attributions and ownerships correct:
>
>On Dec 14, 11:18�am, dkco...(a)panix.com (David Combs) wrote:
>> ....
>> Note: opencsw uses pkgget (same, different from what blastwave used
>> *before* the messy "divorce" at Blastwave between Dennis Clarke and
>> Phillip Brown (went and started opencsw.org),
>
>That paragraph has a very misleading implication.
>
>Better and more appropriately written as
>"Philip Brown (started CSW packaging, wrote pkg-get, moved both to
>opencsw.org)"
>
>and...
>
>
>> whereas Clarke-and-team created "pkgutil" (pkg-util?).
>
>no, "Clarke-and-team" did NOT create pkgutil. Just like he did not
>create CSW packaging. I did. he merely hosted it.
>
>"Clarke" does not own pkgutil, nor did he have much to do with the
>creation of it.
>It was primarily created by (and is still owned and maintained by)
>Peter Bonivart.
>Who has contributed effort to both blastwave, and opencsw.org.
>For those who care, pkgutil works on both repositories, as does pkg-
>get.
>
>
>

Well, thanks for that last, that each of them work the
same on each site.


David


From: John D Groenveld on
In article <hghrjk$7gr$1(a)reader1.panix.com>,
David Combs <dkcombs(a)panix.com> wrote:
>I don't know... it just seems a pity that with
>each of the two sites working so hard, that the
>user cannot use them both. I mean, all the work

Competing CSW package projects should yield happier
CSW package users.

>Anyway, looks like I'm getting nowhere here,
>so if I want a newer emacs than is on blastwave,
>I'll have to grab the sources and build it
>myself. :-(

You might consider volunteering to maintain GNU emacs
for Blastwave if the current maintainer has moved on.

John
groenveld(a)acm.org
From: phil.googlenews on
On Dec 18, 10:24 pm, dkco...(a)panix.com (David Combs) wrote:
> ...
> I don't know... it just seems a pity that with
> each of the two sites working so hard, that the
> user cannot use them both.   I mean, all the work
> that each of the two is doing is for presumably one
> purpose -- to provide software, already compiled, etc,
> to solaris users.  I mean, the more users a site
> gets, the happier the people who put in all the work.


There are a lot of people "working hard", for both debian linux, and
redhat linux.
They are both "linux".
Does that mean if you somehow install both in parallel on the same
running OS, that you get improved benefit from running one of them? I
dont think so.

The sane thing to do, is pick the one that best suits your needs, and
go with it, rather than try to cobble them together.


> Anyway, looks like I'm getting nowhere here,
> so if I want a newer emacs than is on blastwave,
> I'll have to grab the sources and build it
> myself.   :-(

Or just switch over to using opencsw packages.
Which should be almost as simple as editing your pkgutil or pkg-get
config to point to an opencsw repository, and using the "upgrade"
command :-)

From: ChrisS on
On Dec 21, 1:19 pm, "phil.googlen...(a)bolthole.com"
<phil.googlen...(a)bolthole.com> wrote:
> On Dec 18, 10:24 pm, dkco...(a)panix.com (David Combs) wrote:
>
> > ...
> > I don't know... it just seems a pity that with
> > each of the two sites working so hard, that the
> > user cannot use them both.   I mean, all the work
> > that each of the two is doing is for presumably one
> > purpose -- to provide software, already compiled, etc,
> > to solaris users.  I mean, the more users a site
> > gets, the happier the people who put in all the work.
>
> There are a lot of people "working hard", for both debian linux, and
> redhat linux.
> They are both "linux".
> Does that mean if you somehow install both in parallel on the same
> running OS, that you get improved benefit from running one of them? I
> dont think so.
>
> The sane thing to do, is pick the one that best suits your needs, and
> go with it, rather than try to cobble them together.
>
> > Anyway, looks like I'm getting nowhere here,
> > so if I want a newer emacs than is on blastwave,
> > I'll have to grab the sources and build it
> > myself.   :-(
>
> Or just switch over to using opencsw packages.
> Which should be almost as simple as editing your pkgutil or pkg-get
> config to point to an opencsw repository, and using the "upgrade"
> command :-)

Well, though Phill is "plugging" his own site here, he is correct in
one thing; I've used the upgrade option earlier in the year when we
had to make the decision of who to go with, Blastwave or OpenCSW. We
(I), chose to move our platforms to OpenCSW and the upgrade worked
perfect. All the old Blastwave software we had installed (too much or
not) all upgraded just fine. We primarily use SAMP stuff (minus the
MySQL), but it's nice to have those little tools at the ready if
needed.

As a sidebar (but my objective here) I was wondering when Apache2 will
be upgraded on OpenCSW. I see the "Jones" have already update
theirs. {:-) And I'm not mixing the two! I picked my poison.

I use to compile all my own, but in the early days of Solaris 9 (I
think), it was getting to be a real pain since many developers
(Linux), never considered Solaris, so there were always little things
wrong here and there. If only I had the time to fuss with all that
stuff these days. I have less-fun things to worry about. LOL
Besides, when I finally die at my desk with eggnog in-hand and before
the body is even cold the "young-guyz" will be screaming, hooray, the
witch is dead, break out the RedHat boys. Hee, hee. I should change
my handle to something like, old-cranky-dino. Damn I wish we could
have Gmail aliases.

Happy Compiling .... (and Holidays).