On Wed, Apr 25, 2001 at 09:44:52AM -0700, Ralph Zeller wrote:
> Thanks for the tips, Jacob. Debian is so nice...
At least on the prebuilt BINARY package management front...
>
> Apt-move now works perfectly after I punched a hole in my firewall for
> port 873 (rsync). Apt-get is perfectly happy doing http or ftp, but
> apparently apt-move requires rsync to get the Packages.gz files.
>
Should have mentioned this. If you use 'apt-move getlocal', apt-move
will use your local cache of Packages files. I forgot that the
"unstable" version does this by default with 'apt-move get'. Not
really sure why the apt-move in potato doesn't use the local cache,
since you can't apt-get something that's not in your local Packages
cache. Like I said, the apt-move in "unstable" is far superior.
<[EMAIL PROTECTED]>
PS I still think Debian SUCKS for building custom packages.
Just do 'apt-get source -b ssh' for an explanation. Requiring
gnome and X to build ssh? What the #@!?
Or better yet 'apt-get source debhelper debmake'. You can't build
one without the other being installed (not even an older version of
one will work), and these are the packages needed to build the rest
of the .debs.
Debian's great, if you use the 'official binaries', but then I thought
a point of Linux was to be able to "tweak and configure and customize
to your heart's content". Not that this can't be done. It's just that
the apt/dpkg system, IMHO, gets in the way far too often.
Of course, rpm systems aren't any better.
Now on my OpenBSD box, just last night I rebuilt every binary on the
system, including X 4.0.3 - in under 5 hours (fast processor/big RAM helped).
And all I had to know to customize was (a little) C. I've spent well over
5 hours trying to understand all the intricacies of apt/dpkg, and I still
need to know C in the end anyway, as well as how not to break apt/dpkg.
Then I need to build each package separately, which is the real pain in
the behind.
