On Mon, 30 Oct 1995, J.H.M.Dassen wrote:
> [...]
> Desirable goals for source packaging
>
> - Upstream sources should be used unmodified.
>[...]
> - Distribute wholly unmodified source
> - Have the source extracted and patches by a 'debianizer' script.
> Th
J. H. M. Dassen writes:
> The default Linux binary format is to move to ELF. Most of the libraries
> and other support is already debianized, but uses non-standard locations.
> In the long term, we want users to be able to remove the a.out libraries,
> binutils etc, once all their binaries are ELF.
Bill Mitchell writes ("Re: Distribution"):
> Wait a sec. I think we have a definition or a perception problem here.
>
> What is debian 0.93R6?
> 1. Just the install disk set?
> 2. The install disk set plus a frozen set of base packages?
> 3. The install disk set plus a frozen complete distribu
Draft notes:
* Comments that shouldn't appear in the final document are marked in
the following way: ( comment -sr1)
These comments usually highlight open questions. In this case I am
interested in answers. (see next sentence)
* Please send comments about the contents of this document via p
[EMAIL PROTECTED] (Martin Schulze) said:
> So bugfixes et cetera still go into a released release (eh published
> release). So we run into the great slackware problem that there are
> tons of version 2.2 (as an example).
>
> I don't agree to that. [...]
Wait a sec. I think we have a definition o
Hallo Ian Jackson!
}So, what we're left with, if you agree with my release strategy, is:
}
} released -> debian-0.93
} debian-0.93/binary [ bugfixes and urgent releases only ]
} source
} ms-dos
} Packages -> binary/Packages
} disks
So bugfix
Subject: 1.0 issues: Packaging (esp. source)
Short Description
-
There appears to be concensus among the developers that the current
source packaging system, which has debianized source packages,
should be replaced by a system that uses unmodified source.
Desirable goals for sou
Subject: 1.0 issues: FSSTND compliance & preparation for a.out abolishment
Short Description
-
The default Linux binary format is to move to ELF. Most of the libraries
and other support is already debianized, but uses non-standard locations.
In the long term, we want users to be a
Description
---
The Powers That Be (most importantly, the linux libraries maintainers)
have decided to drop both termcap and curses support (they are not
present in the newer ELF libc's for example).
Both of these libraries are replaced by ncurses, which AFAIK uses
the same interface.
Lin
Dear developers,
I'll be listing a couple of issues that I think are relevant for the
development of the 1.0 release. I'll expand them in separate messages.
I'll try not to take sides in debates that'll probably be reopened;
I'm merely trying to provide a framework for the discussion.
Move to EL
Matthew Bailey writes ("Re: package uploading probs "):
> On Mon, 30 Oct 1995, Ian Jackson wrote:
> > chiark.chu.cam.ac.uk:/debian/private/Incoming
> > Matt, can you mirror this somewhere ?
>
> /private/project/incoming-uk
> And should there be a doom subdirectory there?
Oops, that was a mistake.
Package: netstd
Version: 1.20
When mounting an nfs volume with no_root_squash set things worked fine
for a while then my root uid seemed to get squashed for some reason.
Unmounting and mounting again seemed to solve the problem. I'm not
quite sure what caused this.
[kryten:/home/andrew] more /etc
Bdale Garbee writes:
>It is possible to work around this defect by specifying an explicit path for
>more in the user's .mh_profile:
>
> moreproc: /bin/more
Dunno much about MH but your might consider the following for a workaround:
If there is a global config file for mh, you may put it ther
Package: mh
Version: 6.8.3-2
The 0.93R6 MH mail user interface package causes it to be impossible to
read any mail, since the default moreproc is '/usr/bin/more', and the current
Debian release appears to put more in '/bin/more' instead. You end up with
errors like:
[EMAIL PROTECTED]:~:
> I am planning on adapting the information in the /usr/doc/accounting
> texinfo page to a series of `man' pages in the acct package.
> Some might argue that this is redundant and therefore wastes disk
> space and introduces the chance for errors. Others might argue that
> this is a useful complem
I am planning on adapting the information in the /usr/doc/accounting
texinfo page to a series of `man' pages in the acct package.
Some might argue that this is redundant and therefore wastes disk
space and introduces the chance for errors. Others might argue that
this is a useful complement to the
Just finished with my 1st cup of coffee today :)
Nice to see there's some discussion on this topic underway.
Martin Schulze writes:
>Hallo Matthew Bailey!
>
>}> directory across some sites with good connectivity and use rdist(1) to keep
>them
>}> in sync? Major mirror sites might be good candi
Hallo Matthew Bailey!
}> directory across some sites with good connectivity and use rdist(1) to keep
them
}> in sync? Major mirror sites might be good canditates for this.
}>
}I would probably suggest just mirror as a program to keep them up to date.
}If there is a SINGLE site then this would no
On Mon, 30 Oct 1995, Ian Jackson wrote:
>
> chiark.chu.cam.ac.uk:/debian/private/Incoming
>
> Matt, can you mirror this somewhere ?
/private/project/incoming-uk
And should there be a doom subdirectory there?
Just curious...
Matt
19 matches
Mail list logo
