From: David Combs on
In article <hgbn3d$b01a$1(a)tr22n12.aset.psu.edu>,
John D Groenveld <groenvel(a)cse.psu.edu> wrote:
>In article <hgbedv$8m$3(a)reader1.panix.com>,
>David Combs <dkcombs(a)panix.com> wrote:
>>So I (and I guess most users too) would like to have some
>>from you, and some from blastwave, depending on the versions.
>
>Assuming you're attempting to use CSW packages as dependencies
>for your SageMath builds, set up two zones: one with pkg_get pointing
>towards OpenCSW and another pointing towards Blastwave.
>
>John
>groenveld(a)acm.org

OK, sort of neat, good use of zones.

(Gives me a reason to go study zones!)


But if in general yoiu want to run emacs, sometimes emacs-new,
and sometimes emacs-alpha, regardless of the zone you might
be in -- what then?


Thanks!

David


From: John D Groenveld on
In article <hgci9c$cnp$3(a)reader1.panix.com>,
David Combs <dkcombs(a)panix.com> wrote:
>But if in general yoiu want to run emacs, sometimes emacs-new,
>and sometimes emacs-alpha, regardless of the zone you might
>be in -- what then?

If you were my developer, I would tell you to do your development
on your (stationary or mobile) developer workstation and do your
builds against your SageMath subversion or GIT checkouts on your
OpenCSW and Blastwave build zones.

I would ask you if Sun's versions of GNU emacs and SunStudio XEmacs
that ship for Indiana and Nevada are suffient for your developer
workstation.

John
groenveld(a)acm.org
From: phil.googlenews on
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.



From: phil.googlenews on
On Dec 16, 12:03 pm, dkco...(a)panix.com (David Combs) wrote:
> In article <d618eac4-883b-4c4b-8e5b-6a0d169e9...(a)g1g2000pra.googlegroups.com>,
>
> phil.googlen...(a)bolthole.com <phil.googlen...(a)bolthole.com> wrote:
> >On Dec 14, 11:18 am, dkco...(a)panix.com (David Combs) wrote:
>
> >> More to the point, can I get an emacs-21 from Blastwave and an
> >> emacs-23 from csw?  (presumably new libraries from GNU never
> >> invalidate old functions!)
>
> >Err.. why would you want to?
>
>
> Blastwave has lots of stuff, and so do you, but there's
> differences in versions, depending on who updated program
> x first...[snip]..

yes.. but you didnt answer my question.

Why would you deliberately want to keep the older version of emacs
around?
You used it as a 'specific' example, of a need you have.
Was it merely a hypothetical example after all, and you have no actual
*need* to do so?



> So I (and I guess most users too) would like to have some
> from you, and some from blastwave, depending on the versions.
>
> Makes sense to me.

Not to me... You havent said WHY you want would older versions from
blastwave.
Please give specific cases, rather than vague hypotheticals?

From: David Combs on
In article <c7ef6e54-0026-49eb-a1f8-f34fce9abbf1(a)v15g2000prn.googlegroups.com>,
phil.googlenews(a)bolthole.com <phil.googlenews(a)bolthole.com> wrote:
>On Dec 16, 12:03�pm, dkco...(a)panix.com (David Combs) wrote:
>> In article <d618eac4-883b-4c4b-8e5b-6a0d169e9...(a)g1g2000pra.googlegroups.com>,
>>
>> phil.googlen...(a)bolthole.com <phil.googlen...(a)bolthole.com> wrote:
>> >On Dec 14, 11:18�am, dkco...(a)panix.com (David Combs) wrote:
>>
>> >> More to the point, can I get an emacs-21 from Blastwave and an
>> >> emacs-23 from csw? �(presumably new libraries from GNU never
>> >> invalidate old functions!)
>>
>> >Err.. why would you want to?
>>
>>
>> Blastwave has lots of stuff, and so do you, but there's
>> differences in versions, depending on who updated program
>> x first...[snip]..
>
>yes.. but you didnt answer my question.
>
>Why would you deliberately want to keep the older version of emacs
>around?
>You used it as a 'specific' example, of a need you have.
>Was it merely a hypothetical example after all, and you have no actual
>*need* to do so?
>
>
>
>> So I (and I guess most users too) would like to have some
>> from you, and some from blastwave, depending on the versions.
>>
>> Makes sense to me.
>
>Not to me... You havent said WHY you want would older versions from
>blastwave.
>Please give specific cases, rather than vague hypotheticals?
>

I suppose I'd like to keep the old one until I'm sure the new
one is ok. But I can live without that, for sure.

It's just that there's tons of other blastwave software there,
including libraries that emacs might use.

And everyone else in this thread gives their opinion
that you're asking for trouble if you mix stuff from
both sources (you and blastwave) in the same directory,
ie /opt/csw/...

You know, assuming disk has gotten sufficiently cheap,
you could have a parallel opencsw that has all the
same stuff, but compiled etc to work in opencsw.

Then one could easily have stuff from both places,
both being on the PATH.

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.

No way to give feedback (positive) to the group
one's NOT allowed to use, because the decision to
provide only a single place to store the stuff
-- the stuff from ONE of the two sites.

To the extent any anger is involved in the decision
to use /opt/csw, seems to me, gets in the way of
providing services to the Solaris user base.

----

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. :-(


David