[clue-tech] Presentation on Ubunto/Debian?

[Keith Hellman]

On Wed, Jun 01, 2005 at 07:35:42PM -0600, Collins Richey wrote:
> On 6/1/05, David Anselmi <anselmi at anselmi.us> wrote:
> > David Anselmi wrote:
> > [...]
> > > How many packages do you need to build from source?
> > 
> > Sorry that I asked this so poorly.  I meant, "how many packages (gcc,
> > etc) do you need to install before you can build something from source?"
> > 
> 
> That's a fair question, but I don't know the answer. I tried the usual
> suspects (gcc , autoconf, etc.) from a list, but it seemed (missing
> ???.h files, and no I didn't write them down) that some xxxdev
> packages were missing.
> 
> <rant>
> It probably makes sense for a server setup, but I've never understood
> why installs of a package don't include everything. I'm probably
> spoiled by long years on Gentoo, where that's exactly how it works.
> </rant>

I agree.  I've always despised building packages (particularly ones
that RPMs were not available for) on RPM systems because half of my
time would be spent on installing the -dev package for all the
dependencies.  There may be an easy way to do this on RPM systems, but
I never figured it out.

In debian, it is 'apt-get build-dep'.  Then 'apt-get source' pulls the
specified package source (the one you just ran build-dep for).  This is
one of the BIG reasons I switched from SuSE (rpm based) to debian and
haven't looked back since.

YMMV.

PS:  It may appear that my critique is not fair against RPM systems
because if I tried building some new tarball'd package on debian I
would have to (still) figure out which debian development packages I
needed to install for the header files.  BUT, for each of these I would
be able to run 'apt-get build-dep' and pull the dependencies for a
particular 'first tier' package in one fell swoop. (Not that I have to
build stuff often for debian.)

-- 
Keith Hellman                             #include <disclaimer.h>
khellman at mcprogramming.com                from disclaimer import standard
public key @ www.mcprogramming.com


"While it might seem that a simple increment operator is an atomic
operation, there's no gaurantee that it is.  It's actually possible for
Thread 1 to update half of a 32-bit x while Thread 2 reads the full 32
bits, getting a mishmash instead of a valid integer.  (And that's only
one thing that can go wrong.  Another is that compiler optimization might
leave the integer in a register.  You really can't ever let threads
simultaneously access data without protection.)"

-- Marc J. Rochkind, *Advanced Unix Programming*, Second Ed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://cluedenver.org/pipermail/clue-tech/attachments/20050601/477e66b9/attachment.bin