[csw-users] How can I get blastwave's package sources?

[James Lee]

On 17/05/07, 15:36:21, "Trygve Laugstøl" <trygvis at inamo.no> wrote regarding
Re: [csw-users] How can I get blastwave's package sources?:

> > Try asking, specifically what do you want?  They should all archived
> > somewhere.  Note that GPL allows a charge to me made for this service,
> > I'm sure Dennis can provide you with his rates.

> Specifically I want to be able to build any package from Blastwave when
> I want to, assuming I'm online. The main motivation for me is not
> paranoia (I do trust binaries built by you) but learning how to build
> Solaris and Blastwave packages.

Blastwave isn't a free educational service.


> I don't quite see the relevance of the cost of hosting the sources, the
> cost of hosting the binaries will be (is!) *way* bigger.

Cost is important because my local shop does not give away food.  The
hosting of the binaries is done automatically by machines and at no
cost or time penalty to myself - other people's situation and views
may vary.

You assume that the sources (not just the upstream source bundles) are
stored in a form that you can just download and use as a unified entity.
Some are and that is where SVN is helping, but not all are.



> >> I bet that today it is
> >> practically impossible to rebuild any Blastwave release older than a
> >> year or even a half year.
> >
> > I take on your bet, but you have already lost.  The practical problem
> > is reconstructing the environment to build an old package but I have
> > already done it when we needed a back compatible package.  Normally
> > there is no reason to do it.

> I thought (or assumed rather) that the build machine was a plain Solaris
> 8 installation with GCC and/or Sun Studio which should be fairly easy to
> set up locally.

It is, given a few days to load the correct software, that's why you
loose the bet :-) although finding old OS patches with the required
bugs might be hard!  Having the exact same software is important as
you must use compatible headers and libraries from the time you choose.
Generally we choose the present and move forward.





James.