I have decided to adopt the orphaned "videogen" package (bug #122708).
As I am waiting for DAM, I need a sponsor.
The package is lintian and linda clean.
Download: http://smurf.noris.de/code/debian/unstable/source/videogen*
APT: deb-src http://smurf.noris.de/code/debian/ unstable smurf
videogen (
Hi, Aaron Matthew Read wrote:
> 3. For each platform, create a source package, for example: smlnj-x86
>which would contain the appropriate boot image. These packages
>would provide smlnj as a virtual package. Seems the best solution.
4. Package the upstream image files as a (somewhat-)deb
The smlnj package (the compiler) is implemented in sml and needs a
working implementation to build. Upstream, a set of pre-compiled
binary files (~4 MB each) are supplied for each platform.
When I initially supplied the smlnj package, I shortsightedly only
included the binary images required to bu
I have decided to adopt the orphaned "videogen" package (bug #122708).
As I am waiting for DAM, I need a sponsor.
The package is lintian and linda clean.
Download: http://smurf.noris.de/code/debian/unstable/source/videogen*
APT: deb-src http://smurf.noris.de/code/debian/ unstable smurf
videogen (
Hi, Aaron Matthew Read wrote:
> 3. For each platform, create a source package, for example: smlnj-x86
>which would contain the appropriate boot image. These packages
>would provide smlnj as a virtual package. Seems the best solution.
4. Package the upstream image files as a (somewhat-)deb
The smlnj package (the compiler) is implemented in sml and needs a
working implementation to build. Upstream, a set of pre-compiled
binary files (~4 MB each) are supplied for each platform.
When I initially supplied the smlnj package, I shortsightedly only
included the binary images required to bu
Hello. I've put together a package for par2cmdline and would like to get
it into Debian. I am not a maintainer and, obviously, would need a sponsor
for this package.
par2cmdline is a unix client for parchive's second specification. It's a
fairly small package. Took me about 3 hours t
Hello. I've put together a package for par2cmdline and would like to get
it into Debian. I am not a maintainer and, obviously, would need a sponsor
for this package.
par2cmdline is a unix client for parchive's second specification. It's a
fairly small package. Took me about 3 hours t
On Tue, Jul 15, 2003 at 05:07:00PM +0200, GCS wrote:
> I would like to install postgres into a chroot environment, where the
> postinst script can't ask for the path where to create the database
> directory etc. How can I preset these data (like db_fset), so the
> postinst script can get the data
OK, this is not a C language help list, nor a libreadline man^winfo page.
However..:
Barry Pollock wrote:
> line_read = readline ("");
> /* If the line has any text in it, save it on the history.
> The control -D must be intercepted here */
So what is your problem?
> if (line_read && *lin
On Tue, Jul 15, 2003 at 05:07:00PM +0200, GCS wrote:
> I would like to install postgres into a chroot environment, where the
> postinst script can't ask for the path where to create the database
> directory etc. How can I preset these data (like db_fset), so the
> postinst script can get the data
OK, this is not a C language help list, nor a libreadline man^winfo page.
However..:
Barry Pollock wrote:
> line_read = readline ("");
> /* If the line has any text in it, save it on the history.
> The control -D must be intercepted here */
So what is your problem?
> if (line_read && *lin
On Tue, Jul 15, 2003 at 07:49:16PM +0200, Luk Claes wrote:
> Hi
>
> How does one make a package description where the line breaks at an
> intended way?
>
> See bug 180727.
RTFM:
http://www.de.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description
especially:
The lines in the extend
On Tue, Jul 15, 2003 at 07:49:16PM +0200, Luk Claes wrote:
> How does one make a package description where the line breaks at an
> intended way?
>
> See bug 180727.
Indent the preformatted portions of the description by one extra space.
In this example, the description should read:
Description:
Hi
How does one make a package description where the line breaks at an
intended way?
See bug 180727.
All remarks are welcome.
Kind regards
Luk
---
GPG Fingerprint : C061 8F2E EA93 43DE 08D5 71EA 02DF 840B 1B57 0E7C
On Tue, Jul 15, 2003 at 07:49:16PM +0200, Luk Claes wrote:
> Hi
>
> How does one make a package description where the line breaks at an
> intended way?
>
> See bug 180727.
RTFM: http://www.de.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description
especially:
The lines in the extende
On Tue, Jul 15, 2003 at 07:49:16PM +0200, Luk Claes wrote:
> How does one make a package description where the line breaks at an
> intended way?
>
> See bug 180727.
Indent the preformatted portions of the description by one extra space.
In this example, the description should read:
Description:
Hi
How does one make a package description where the line breaks at an
intended way?
See bug 180727.
All remarks are welcome.
Kind regards
Luk
---
GPG Fingerprint : C061 8F2E EA93 43DE 08D5 71EA 02DF 840B 1B57 0E7C
--
To UNSU
Dear Mentors,
I would like to install postgres into a chroot environment, where the
postinst script can't ask for the path where to create the database
directory etc. How can I preset these data (like db_fset), so the
postinst script can get the data via db_get? Or should I tamper with the
postin
Dear Mentors,
I would like to install postgres into a chroot environment, where the
postinst script can't ask for the path where to create the database
directory etc. How can I preset these data (like db_fset), so the
postinst script can get the data via db_get? Or should I tamper with the
postin
The control -D character must b prevented from reaching the history
The program must be able to receive a `\n' by itself in order to
function properly.
You can see it at http://www.hurontel.on.ca/~barryp/ed
Here is the code in question!
char *
rl_gets ()
{
register int i = 0;
/* If the buffer
The control -D character must b prevented from reaching the history
The program must be able to receive a `\n' by itself in order to
function properly.
You can see it at http://www.hurontel.on.ca/~barryp/ed
Here is the code in question!
char *
rl_gets ()
{
register int i = 0;
/* If the buffer
Hi, Pete Ryland wrote:
> Ctrl-D is not a 'signal' as such, but simply will cause any reads from
> stdin to report EOF.
... if you're reading "cooked" standard input. Readline doesn't; for
readline, ^D is just another character, and what happens when the user
pressed ^D is a matter of (for the use
On Tue, Jul 15, 2003 at 05:18:06AM -0400, Barry Pollock wrote:
> I need to trap the Control-D signal long enough for my program to run its
> quit program when using readline. I get an error in the strcpy function
> when using readline.so. If i disable readline first and allow the memory
> to be fre
I need to trap the Control-D signal long enough for my program to run
its quit program when using readline. I get an error in the strcpy
function when using readline.so. If i disable readline first and allow
the memory to be freed properly, the Control -D exit is proper.
Barry
Hi, Pete Ryland wrote:
> Ctrl-D is not a 'signal' as such, but simply will cause any reads from
> stdin to report EOF.
... if you're reading "cooked" standard input. Readline doesn't; for
readline, ^D is just another character, and what happens when the user
pressed ^D is a matter of (for the use
On Tue, Jul 15, 2003 at 05:18:06AM -0400, Barry Pollock wrote:
> I need to trap the Control-D signal long enough for my program to run its
> quit program when using readline. I get an error in the strcpy function
> when using readline.so. If i disable readline first and allow the memory
> to be fre
I need to trap the Control-D signal long enough for my program to run
its quit program when using readline. I get an error in the strcpy
function when using readline.so. If i disable readline first and allow
the memory to be freed properly, the Control -D exit is proper.
Barry
--
To UNSUBSCRIBE
28 matches
Mail list logo
