'Ian Jackson wrote:'
>
>I think I'll have to support `Replaces' or something, so that old
>packages can have all their files `taken away' and disappear
>eventually.
Here's the scenario that I hope a Replaces fiels might resolve. I'm
working on the S-lang library. Both most and Midnight Commander
Raul Miller writes ("Re: binary-alpha and binary-sparc directories"):
> How about the option of a better record of what has happened?
>
> For example, currently, if multiple packages supply the same file only
> the most recently installed package has the files listed in it&
Bill Mitchell writes ("Re: binary-alpha and binary-sparc directories"):
> This seems shakey -- especially if we posit that the i386 maintainer
> is in the U.S., the Mac maintainer in Germany, and the PowerPC maintainer
> in Korea. Also, the upstream source maintainer might b
> > > The way I see this working, architecture-specific maintainers with
> > > the ability to address architecture-specific bug reports and do
> > > architecture-specific testing would feed architecture-specific
> > > fixes and patches to the primary package maintainer. Primary
> > > package maint
Raul Miller:
> I think this is a bug in the debian packaging mechanisms.
Ian Jackson:
Well, I could change dpkg so that it would barf in this situation,
rather than going ahead and removing the files from the earlier
package, but I think that would have been less helpful.
How about th
Hi,
Ian Jackson wrote:
> As Matt Bailey suggests, I think separate Incoming directories is a
> better solution.
I'm from the m68k section, and although it's kind of you to set up the
directories for our uploads, I believe the main development of Debian/m68k
is going to be done with the german ft
(Gigantic crosspost trimmed.)
Raul Miller writes ("Re: binary-alpha and binary-sparc directories"):
> It does look like dvips was superceeded by some other package, and
> that it did originally have some executables in it. [All I have on my
> system from dvips is a copyright
Michael K. Johnson writes ("Re: binary-alpha and binary-sparc directories "):
> Ian Murdock writes:
> [...] ther have to have separate Incoming directories for all
> >supported architectures, or we'll have to have a naming scheme for all
> >Incoming binary pa
Chris Fearnley writes:
> '[EMAIL PROTECTED] wrote:'
> >I had moaned about this weeks ago. You have to manually delete dvips after
> >installing dvipsk, xdvi after xdvik etc. A "Conflicts:" in debian.control
> >might have helped here. Or a new "Replaces:" field.
>
> Yes, this seems to me a good ide
(Crosspost to -alpha and -sparc removed.)
Bill Mitchell writes ("Re: binary-alpha and binary-sparc directories"):
> It seems that the Guidelines document needs updating to address
> issues falling out of this.
>
> One issue is whether binary packages are to be distingui
Juergen Menden:
any package which needs to be compiled is of course not
arch-independent. on my system here (sunos, not debian ;-)) at
least the following are partially compiled:
> ii dvips5.58f 2TeX DVI-driver for Postscript
> ii fort77 1.6 1An f2
'[EMAIL PROTECTED] wrote:'
>
> Raul Miller writes:
> Raul> It does look like dvips was superceeded by some other package, and
> Raul> that it did originally have some executables in it.
>
>Nils switched to the upstream convention of reflecting the 'k' for Karl
>Berry's kpathsea in the package n
[This goes to debian-devel only.]
Raul Miller writes:
Raul> It does look like dvips was superceeded by some other package, and
Raul> that it did originally have some executables in it.
Nils switched to the upstream convention of reflecting the 'k' for Karl
Berry's kpathsea in the package
Raul Miller wrote lately:
>
> Ian Murdock:
>I doubt there'll be a substantial number of architecture-neutral
>packages; we can either copy or link them into all of the trees.
>
> I suppose this depends on what you mean by substantial... Here's a
> list of packages that appear to be archi
Ian Murdock:
I doubt there'll be a substantial number of architecture-neutral
packages; we can either copy or link them into all of the trees.
I suppose this depends on what you mean by substantial... Here's a
list of packages that appear to be architecture-neutral, by cursory
examination o
Ian Murdock writes:
ther have to have separate Incoming directories for all
>supported architectures, or we'll have to have a naming scheme for all
>Incoming binary packages (prepending a dash and the architecture name,
>for example) that can be easily resolved before the packages are moved.
Cons
Date: Fri, 29 Dec 95 17:51 EST
From: Raul Miller <[EMAIL PROTECTED]>
How should we distinguish between i386/m68k/sparc specific packages
and architecture neutral packages?
As I envision it, we'll have a structure like this:
debian-1.1/
debian-1.1/binary-alpha/
debian-1.1/binary-alpha
On Fri, 29 Dec 1995, Ian Murdock wrote:
> be maintained just like the i386 version is maintained. (That is,
> contributors upload packages to an Incoming directory and I move them into
> the archive from there.)
No a problem, but we will need more incomings to help keep the sort down.
--
Matthe
Matthew Bailey:
> For those out there that are interested. I will make space available for
> these ports, and allow each group to maintain uploads for the subtree.
>
> Please contact me if you are in need of an account for this use.
Ian Murdock:
Please don't do this. I'd rather t
On Wed, 27 Dec 1995, Matthew Bailey wrote:
> For those out there that are interested. I will make space available for
> these ports, and allow each group to maintain uploads for the subtree.
>
> Please contact me if you are in need of an account for this use.
Please don't do this. I'd rather t
On Wed, 27 Dec 1995, Dominik Kubla wrote:
> you might as well add binary-m68k since the first Debian/68k packages
> are starting to appear.
Okay.
> These packages as well as the necessary source patches are currently
> stored at U-Mainz:
>
> ftp.uni-mainz.de:/pub/Linux/devel/debian/dontuse/m6
For those out there that are interested. I will make space available for
these ports, and allow each group to maintain uploads for the subtree.
Please contact me if you are in need of an account for this use.
--
Matthew S. Bailey
107 Emmons Hall
Central Michigan University
Mt. Pleasant, MI 4885
Hello Ian,
you might as well add binary-m68k since the first Debian/68k packages are
starting to appear. These packages as well as the necessary source patches
are currently stored at U-Mainz:
ftp.uni-mainz.de:/pub/Linux/devel/debian/dontuse/m68k/
Curently the follwing packages are available
Also, don't forget about architecture-independent binaries...
--
Raul
On Sat, 23 Dec 1995, Ian Murdock wrote:
> I've created binary-alpha and binary-sparc directories under the
> development tree. They're both empty at the moment, of course, but
> they're ready for use whenever the development teams have something
> to put there.
>
> (BTW, I plan to rename binary
25 matches
Mail list logo
