Package management

[Christopher Schmidt]

On Tue, May 15, 2007 at 01:40:50PM -0400, Paul Lussier wrote:
> virginsnow at vfemail.net writes:
> 
> >> From: Paul Lussier <p.lussier at comcast.net>
> >> Date: Tue, 15 May 2007 11:34:21 -0400
> >> Cc: gnhlug-discuss at mail.gnhlug.org
> >
> >>  $ apt-get source foo=<desired package number>
> >>  $ cd foo-<version number>
> >>  $ dpkg-buildpackage -rfakeroot
> >>  $ cd .. && dpkg -i foo-<version number>
> >
> > I think you forgot to apt-get build-deps or whatever that OTHER debian
> > magic command is.
> 
> Perhaps,  though I've never done that.
> 
> > # emerge =dev-lang/python-2.4.2
> >
> > and find something to do for 1/2 an hour.
> 
> Does that install the package for you, build a package you can then
> use elsewhere, or both?  It is entirely possible/reasonable that I
> would want to build a package to install elsewhere without actually
> installing said package on the build system.  In which case, a command
> which installs it for me but does not leave the package behind is
> useless to me. As is a system which both installs and builds the
> package.

'emerge' is similar to 'apt', in that it is a top level command which
ties together lots of smaller commands, iirc. So, although that command
will build+install, there are also commands to just build, and just
install, if memory serves.

Regards,
-- 
Christopher Schmidt
Web Developer