On Mon, Nov 09, 1998 at 10:13:07AM -0500, Thomas Bushnell, BSG wrote:
>
>From: Gordon Matzigkeit <[EMAIL PROTECTED]>
>Date: 06 Nov 1998 12:20:15 -0600
>
>Basically, dpkg is not suitable for cross-platform installations,
>because the --instroot option uses the chroot call, which br
On Sun, Nov 08, 1998 at 10:50:05PM -0600, Gordon Matzigkeit wrote:
>
> This is also useful so that people with non-Debian systems can get
> involved with cross-compiling. You don't need a fully dpkg-managed
> Hurd platform to be able to cross-compile .debs.
Well, you need dpkg and friends to bui
From: Gordon Matzigkeit <[EMAIL PROTECTED]>
Date: 06 Nov 1998 12:20:15 -0600
Basically, dpkg is not suitable for cross-platform installations,
because the --instroot option uses the chroot call, which breaks all
the installation scripts (i.e. they see only Hurd binaries, rather
On Sat, 7 Nov 1998, Marcus Brinkmann wrote:
> Good News:
> [...]
>
> ++
> | unpacked |
> | The package is unpacked, but not configured. |
> +
Hi!
> Jules Bean writes:
JB> --On Sat, Nov 7, 1998 5:53 pm +0100 "Marcus Brinkmann"
JB> <[EMAIL PROTECTED]> wrote:
>>> 3) They have some non-Hurd-based system, and a free partition (or
>>> disk space for a subdir install). I'm very interested in
>>> supporting this case, because the va
--On Sat, Nov 7, 1998 5:53 pm +0100 "Marcus Brinkmann"
<[EMAIL PROTECTED]> wrote:
>> 3) They have some non-Hurd-based system, and a free partition (or disk
>> space for a subdir install). I'm very interested in supporting this
>> case, because the vast majority of people interested in the Hurd ar
Hi!
On Sat, Nov 07, 1998 at 10:27:52AM -0600, Gordon Matzigkeit wrote:
> 2) They have an existing Hurd system, but no dpkg. The approach is to
> install dpkg, then it becomes case #1.
This can be done, but it is not trivial, as Dpkg will not know about
existing files. This is similar to moving a
Hi!
> Roland McGrath writes:
RM> We need someone (you? Gord?) to come up with a hurd "base"
RM> package that has just enough to get a system that can run dpkg.
RM> This needs grub, gnumach, libc shared objects, and the base hurd
RM> servers and shared libs.
This is what I've been working
On Fri, Nov 06, 1998 at 06:09:31PM -0500, Roland McGrath wrote:
> >
> > I am not sure what you mean. I'mnot sure if there is an option for dpkg to
> > not run them. You could write a small script which removes the scripts from
> > the package before installation.
>
> No, I want something clean (i
On Fri, Nov 06, 1998 at 06:09:31PM -0500, Roland McGrath wrote:
> > 3) If you want to move things around (configuration files), sometimes a
> >preinst is necessary.
>
> What do you mean exactly? Can you give an example?
Autoconf:
#! /bin/sh -e
test -e /etc/autoconf/acconfig.h && exit 0
test
> There are different cases where a preinst is needed (not every package has
> it) [then list may be far from complete]:
>
> 1) You have a link on the system you want to remove before the package is
>unpacked.
> 2) You have f*cked up completely in a prior package and needs to fix it
>befor
On Fri, Nov 06, 1998 at 05:27:26PM -0500, Roland McGrath wrote:
> > The installation process is a bit difficult. There are four scripts,
> > {pre,post}{rm,inst} which are run before and after removal or installation
> > of packages. The scripts are run with an argument, which defines if it is an
>
> The installation process is a bit difficult. There are four scripts,
> {pre,post}{rm,inst} which are run before and after removal or installation
> of packages. The scripts are run with an argument, which defines if it is an
> upgrade, a new install, a removal or purge (removes configuration too)
On Fri, Nov 06, 1998 at 04:06:12PM -0500, Roland McGrath wrote:
> > > Basically, dpkg is not suitable for cross-platform installations,
> > > because the --instroot option uses the chroot call, which breaks all
> > > the installation scripts (i.e. they see only Hurd binaries, rather
> > > than the
Roland McGrath <[EMAIL PROTECTED]> wrote:
> Is the problem that there are "post-install" scripts and the like that are
> essentially shell scripts that must be run native? Can the installation of
> files, which can be done "cleanly" to another filesystem, and the running
> of scripts, be separated
> > Basically, dpkg is not suitable for cross-platform installations,
> > because the --instroot option uses the chroot call, which breaks all
> > the installation scripts (i.e. they see only Hurd binaries, rather
> > than the current system's). There's no easy solution to this problem,
> > aside
On Fri, Nov 06, 1998 at 12:20:15PM -0600, Gordon Matzigkeit wrote:
> Hi, all!
>
> I've finally got a working Hurd platform again, so I've been seeing
> what can be done to make it easier for people to start installing and
> using Debian GNU/Hurd packages.
Great News. I have finished some weired h
Hi, all!
I've finally got a working Hurd platform again, so I've been seeing
what can be done to make it easier for people to start installing and
using Debian GNU/Hurd packages.
Basically, dpkg is not suitable for cross-platform installations,
because the --instroot option uses the chroot call,
18 matches
Mail list logo
