wg-dev [!hurd-i386], groff
>
>or:
>
>Build-Depends-Indep: debhelper (>= 2), libncurses-dev, xlib6g-dev, groff
>Build-Depends: xlib6g-dev [!hurd-i386], xviewg-dev [!hurd-i386]
>
>?
The former looks more appropriate.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ead the documentation but I´ve know idea why there is
>> this problem. Can anybody help me?
>
>http://sourceforge.net/contact.php
... and it'll help if you give the SourceForge people more information
than "something goes wrong", or they
up my application and send it to the DAM. Would anyone like to
sponsor me in the meantime? If so, I'll file an ITA.
[1] Linux 2.2 has a more flexible way of handling it, but the userspace
tools are much more difficult to use.
--
Colin Watson [EMAIL PROTECTED]
eems to think Linux is SysV (well, it sort of is ...), and
redefines loads of stuff Linux already has. Getting rid of that causes
more problems, though (starting with parameter types to signal() being
wrong); let us know how far you get.
--
Colin Watson [EMAIL PROTECTED]
e both outside and inside Debian, so I don't think
you have to faithfully record which is which while a package is in
development.
--
Colin Watson [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
>Is there any guide, hints or example package in order to
>make a package containing perl scripts & perl modules?
>(No compiled sources at all)
Try the Perl policy, in perl-5.6-doc or similar:
/usr/share/doc/perl-5.6-doc/perl-policy/.
--
s, lintian
flagged them as an unknown field.
[...]
-- Sean 'Shaleh' Perry <[EMAIL PROTECTED]> Fri, 1 Sep 2000 15:35:03 -0700
Try upgrading to the version of lintian in unstable (which has generally
better checks anyway). It should install cleanly on potato systems.
--
Colin Watson [EMAIL PROTECTED]
s wierd.
The .changes file contains the md5sums of the files you're uploading,
including any architecture-specific .deb. There will be separate
.changes files generated for each different architecture as your package
is ported.
--
Colin Watson [EMAIL PROTECTED]
also serves as a handy build-dependency
checker), copy the package into the chroot, and dpkg-buildpackage as
usual.
--
Colin Watson [EMAIL PROTECTED]
;new-postrm abort-install old-version' is called; when
'new-preinst install' fails, 'new-postrm abort-install' is called. So if
your preinst's install step calls useradd, you should unwind that with
userdel in the postrm's abort-install step.
--
Colin Watson [EMAIL PROTECTED]
I intend to adopt browser-history from Karl M. Hegbloom, but I'm still
in the NM queue. Would anyone like to sponsor this package? I have an
upload of version 2.8-2 prepared, which can be found at
http://www.chiark.greenend.org.uk/~cjwatson/debian/>.
Thanks,
--
Coli
"Oliver M . Bolzer" <[EMAIL PROTECTED]> wrote:
>On Sun, Jan 14, 2001 at 01:57:41AM +, Colin Watson
><[EMAIL PROTECTED]> wrote...
>> I intend to adopt browser-history from Karl M. Hegbloom, but I'm still
>> in the NM queue. Would anyone like to
hack together a Debian native
package for the time being. When releases with purely packaging changes
are infrequent, this can make sense. As stability approaches, though,
eventually the package should gravitate towards the "written especially
for Debian" definition.
--
Colin Watson [EMAIL PROTECTED]
are built on a number of different
architectures.
--
Colin Watson [EMAIL PROTECTED]
ing like this:
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
INSTALL = install -s
else
INSTALL = install
endif
install:
$(INSTALL) foo debian/package/usr/bin/foo
HTH,
--
Colin Watson [EMAIL PROTECTED]
Florian Hinzmann <[EMAIL PROTECTED]> wrote:
>On 24-Jan-2001 Colin Watson wrote:
>> Section 4.1 of policy 3.2.0.0/3.2.1.0, or section 11.1 of policy 3.2.1.2
>> now that the packaging manual has been merged.
>
>Oh, merged? So all important information included in
>
Florian Hinzmann <[EMAIL PROTECTED]> wrote:
>On 25-Jan-2001 Colin Watson wrote:
>> Most of the example code I showed was just setting Makefile variables,
>> so it should go outside any targets (normally near the top of
>> debian/rules). Depending on the structure of
es upstream, though, and keeping a
log of everything you do, there should be no problem. I certainly
wouldn't have any qualms about applying a patch that was already in
upstream CVS or whatever, which fixed an annoying bug, but which just
hadn't made it into an upstream release yet.
--
Colin Watson [EMAIL PROTECTED]
doesn't seem like a problem with your package.
--
Colin Watson [EMAIL PROTECTED]
agent (for sendmail),
libgnome-dev (for gnome-config), libncurses5-dev (for termcap.h),
and zlib1g-dev (for zlib.h). Some of these seem a bit unlikely for a
library - BZIP2_PATH and SENDMAIL_PATH don't actually seem to be
used, so perhaps the che
arameters that tell update-rc.d
>what params to use to setup the init script. However, I want to control the
>two output packages seperately.
Call dh_installinit twice, using the -p flag (before --, of course) to
control which package gets altered in eac
ch was in ./lib/Channel.C)
>to #include "../include/waili/Channel.h"
>and such for the rest.
I would use a -I switch instead. Patching the locations of header files
in the source code itself feels wrong, and is less clean.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
rring to this dcgettext__ symbol, not the gettext
executable ... What are those trailing underscores doing there? Am I
being dim?
--
Colin Watson [EMAIL PROTECTED]
t's in unstable, it's just in contrib. If jde depends on it, you'll
need to move that into contrib too.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ostrm
abort-upgrade' and 'postrm abort-install' need to move the file back if
possible.
--
Colin Watson [EMAIL PROTECTED]
se's; would people have set the severity to
'fixed' under those circumstances before tags were implemented? All "new
upstream" version bugs could be tagged fixed straight away if your
definition is right ...
I prefer to just send a note to the bug saying that it *will be* fixed
soon.
--
Colin Watson [EMAIL PROTECTED]
"Steve M. Robbins" <[EMAIL PROTECTED]> wrote:
>True or False: a .deb may NOT contain hard links ?
False. perl-base contains some, for instance.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ngelog debian/tmp/usr/share/doc/{package}/changelog.Debian
>
>in debian/rules.
Why couldn't you use 'dh_installchangelogs ChangeLog' to achieve the
same effect? I wouldn't mention it except that you specifically said
"not with debhelper".
--
Colin Watson [EMAIL PROTECTED]
modified.
Sounds like a large amount of extra error-prone work to me, although I
suppose running dh_make every so often is one way of keeping some bits
of policy vaguely up to date. I just use uscan/uupdate to unpack the new
source and try to apply the old diffs for me.
--
Colin Watson [EMAIL PROTECTED]
ich don't
>explain that much, and don't seem very readable ...
Looking at multi-binary packages by competent maintainers?
--
Colin Watson [EMAIL PROTECTED]
probably the most
common complaint I hear about man.
man may stop supporting this in the future, precisely because it
unavoidably causes such a usability problem immediately after you've
installed some new man pages which it has to search. I should really
find out how
[EMAIL PROTECTED] (Colin Watson) wrote:
>Bob Hilliard <[EMAIL PROTECTED]> wrote:
>> The gzip package has a similar situation with gunzip and zcat,
>>but it has created gunzip.1 and zcat.1 as hardlinks to gzip.1. Since
>>man can deal with a manpage with multipl
Joey Hess <[EMAIL PROTECTED]> wrote:
>Colin Watson wrote:
>>You should not create hard links in the manual page directories, nor
>>put absolute filenames in .so directives.
>
>Heh. There's a man page somewhere in debian that looks something like:
>
>
&
f the package worry about cleaning up after itself.
The main situation where you need to be concerned about old versions of
your package is where you've previously made a mistake in the maintainer
scripts.
--
Colin Watson [EMAIL PROTECTED]
re a more generic approach?
File bugs and wait. Section 8.2.1 of the developer's reference describes
when you can do source NMUs as a porter; it's shorter than for
non-porters, although at least for unreleased architectures it's not a
bad idea to give the maintainer a bit of cl
ime ago, so I doubt it.
Most people [1] who use a helper package these days use debhelper.
>Also, why is chown failing? What's it trying to chown the files to?
root, probably, who's supposed to own documentation files.
>The structure of my source tree is as follows:
[EMAIL PROTECTED] (Colin Watson) wrote:
>debmake/debstd's development was frozen some time ago, so I doubt it.
>Most people [1] who use a helper package these days use debhelper.
[1] http://kitenet.net/programs/debhelper/stats/
--
Colin Watson
on it. It's not clear that use of debmake can
be considered a bug unless it's actually broken.
Maybe the package description should just mention that it isn't being
developed any more.
--
Colin Watson [EMAIL PROTECTED]
e extended in the future to
be able to exclude certain directory trees, and /usr/share/doc is one of
the main directories people might want to exclude. See bug #87711.
--
Colin Watson [EMAIL PROTECTED]
ng dh_make-generated stuff, try
/usr/share/debhelper/dh_make/debianm/rules for an example. It passes -a
and -i to various debhelper commands to work on architecture-dependent
and -independent binary packages respectively. Aside from that you need
to have the appropriat
Am I using the wrong syntax ? I'm using debhelper 3.0.19.
You're slightly out: see update-rc.d(8). You probably want something
more like:
dh_installinit -- defaults 90 10
Cheers,
--
Colin Watson [EMAIL PROTECTED]
e of the package to bar-0.2.tar.gz)
>>
>> The only thing which comes to my mind is treating the old package
>> as 'conflict' for the new one, but there must be a more elegant
>> solution!?
>
>Michael,
>Use Conflicts: foo, and Replaces: foo.
Plus Provid
issing bugs #82479, #92236, #93655, and #95283. ;) As far as I
know, debhelper's code is fine - no doubt Shaleh would appreciate it if
somebody came up with a good patch for lintian.
--
Colin Watson [EMAIL PROTECTED]
t
disclaimer of copyright from the authors. (That is, "no copyright" means
that it defaults to us not being able to use it at all - public domain
takes an explicit statement of renunciation of copyright.)
Something like the X11 licence (http://www.x.org/terms.htm) might be a
reasonably simple one to recommend.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
>in /usr/share?
/usr/share/ is usual, and mentioned (if not mandated?) in
policy, but (personally) I would say that anything that's not too
confusing and that's in a namespace you clearly own is OK. The name of a
binary you install sounds like it qualifies.
--
Colin Watson
got error messages on a missing file in app-defaults.
Yes. [rummages] See current policy, section 12.8.6.
--
Colin Watson [EMAIL PROTECTED]
h and interests.
You should be able to mail [EMAIL PROTECTED] and ask.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
e of the build. debian/files shouldn't be
shipped with the source package; in fact, lintian will complain if you
do.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Wed, 13 Jun 2001 at 18:05:58 +0200, Domenico Andreoli wrote:
> On Tue, Jun 12, 2001 at 06:29:22PM +0100, Colin Watson wrote:
> > I'm very glad to hear that work's being done on dpkg-source that should
> > (if I understand it correctly) obsolete this hack.
>
> m
nst and I don't have the unpacked
files handy at that point to do additional replacement logic myself.
--
Colin Watson [EMAIL PROTECTED]
tecture(s)). If it's out of
date, that will keep it out of testing.
--
Colin Watson [EMAIL PROTECTED]
Stefano Zacchiroli <[EMAIL PROTECTED]> wrote:
>On Wed, Jun 20, 2001 at 06:47:05PM +0100, Colin Watson wrote:
>> If it's out of date, that will keep it out of testing.
>
>what does "out of date" mean in this contest?
It means that the most recent source version
[EMAIL PROTECTED] (Colin Watson) wrote:
>Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
>>On Tue, 19 Jun 2001, Steve M. Robbins wrote:
>>> What if you MOVED the file, rather than copying it: would dpkg still
>>> complain?
>>
>>Do it in prei
d(7)-using package depends on
manpages.)
--
Colin Watson [EMAIL PROTECTED]
t;undocumented(7).
The reporters of #32019 and #53214 both did, although I suppose
debootstrap is making it more and more likely that people will have
things like manpages installed.
--
Colin Watson [EMAIL PROTECTED]
root -g root `pwd`/esms `pwd`/debian/tmp/usr/bin/esms
You aren't using DH_COMPAT=2 or 3, are you? When that is set, the
various debhelper commands (like dh_installdocs, which is installing
your documentation, and dh_builddeb, which calls dpkg to construct the
.deb
'd been pointing people at the version in incoming),
I'd build with 'dpkg-buildpackage -v'.
--
Colin Watson [EMAIL PROTECTED]
means -- try "man undocumented" if you are unsure.
It seems a bit silly, because, well, that's what undocumented(7) says
except in less detail. It also seems like more cruft in the already
crufty man binary. Feel free to write a patch if you t
the files
are still owned by your ordinary user account after the build finishes.
To see what the binary package contains without installing it, use
'dpkg-deb -c foo.deb'.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
CTED] ~]$ fakeroot
[EMAIL PROTECTED] ~]# touch foo
[EMAIL PROTECTED] ~]# chown bin foo
[EMAIL PROTECTED] ~]# ls -l foo
-rw-rw-r--1 bin root 0 Jul 19 21:40 foo
--
Colin Watson [EMAIL PROTECTED]
o version 4, be aware that Markus Hetzmannseder
has packaged that (as gap4* - I've just realized that some of them are
sitting in incoming/REJECT though, bah), and I'm sponsoring him. That
said, he hasn't responded to my mails about problems in the packages.
--
Colin Watson [EMAIL PROTECTED]
tory, so:
$(MAKE) install prefix=$(CURDIR)/debian/tmp/usr \
localstatedir=$(CURDIR)/debian/tmp/var \
sysconfdir=$(CURDIR)/debian/tmp/etc
> dh_suidregister
In testing/unstable, dh_suidregister has been obsoleted in favour of the
dpkg-statoverride mechanism.
--
Colin Watson [EMAIL PROTECTED]
On Fri, Aug 03, 2001 at 01:15:30PM -0300, Gustavo Noronha Silva wrote:
> Em Fri, 3 Aug 2001 08:06:13 -0500
> Colin Watson <[EMAIL PROTECTED]> escreveu:
>
> > > # Add here commands to install the package into debian/tmp.
> > > $(MAKE) install prefix=`pwd`/deb
nything other than that line
>
> $default_host = "master";
Since you're not a Debian developer, you can't use debrelease/dupload to
upload to master.debian.org (it should be ftp-master.debian.org now
anyway). What are you trying to use debrelease for?
--
Colin Watson [EMAIL PROTECTED]
On Fri, Aug 03, 2001 at 11:27:55PM +0430, Pratik Sinha wrote:
> On Fri, 3 Aug 2001, Colin Watson wrote
> > Since you're not a Debian developer, you can't use debrelease/dupload to
> > upload to master.debian.org (it should be ftp-master.debian.org now
> > anyw
This is currently version 2.95.4 for this architecture (i386).
--
Colin Watson [EMAIL PROTECTED]
able.
>
> What should I do to get rid of them?
Try 'echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses'. To
make this permanent, put 'net/ipv4/icmp_ignore_bogus_error_responses=1'
in /etc/sysctl.conf.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
k it's a
> Debian-native package? What did I do wrong?
You should rename eazel-engine-0.3.tar.gz to
eazel-engine_0.3.orig.tar.gz (make sure the hyphens and underscores are
as shown there) and rebuild. That way the tools will notice that an
upstream archive is available and build the .diff.gz against that.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
; > and package is not configured after installation. What to do?
>
> You need to call at least one db_ command in your postinst.
> If you have none, db_version or some such thing should do just fine.
No, you need to source /usr/share/debconf/confmodule. It doesn't matter
whether
r each architecture decide.
The default for i386 is still gcc 2.95.4.
--
Colin Watson [EMAIL PROTECTED]
, so
> > simply writing #!/bin/sh in the script is not sufficient.
>
> I tried ash, it gave the error:
>
> [: ==: unexpected operator
That one's easy, = instead of == is more portable in test (or [)
constructs.
--
Colin Watson [EMAIL PROTECTED]
"$(echo *.foo)" = "*.foo" ] || for X in *.foo ; do foo "${X}"; done
There might actually be a file called "*.foo" :-)
I'd probably give up and use find/xargs instead myself.
--
Colin Watson [EMAIL PROTECTED]
--
goes, no schedule as such, but it's certainly planned
and is reasonably high up the list. I'd be surprised if there weren't
already a bug filed about it, but even if there isn't it's known.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIB
ator
> capable of running most PowerPC operating systems
It's kind of disappointing that this hasn't been ported to powerpc
itself. :( (Take a look at src/cpu_generic/ppc_tools.h for starters.)
Since ppc_tools.h currently hardcodes HOST_IS_X86, I suspect this
release will only bu
Furthermore it won't actually close the bug as apparently desired. See
the policy manual for the syntax of "closes".
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cludes it should not run
> ldconfig.
And what's it doing messing about in /tmp?
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
it
> > doesn't matter if they co-exist?
>
> i think the correct way is to retitle the RFP to ITP and change the
> submitter to yourself
No, don't change the submitter; change the owner instead. See
http://www.debian.org/devel/wnpp/ for instructions.
--
Colin Watson
On Wed, May 05, 2004 at 09:31:10PM +0200, Andreas Barth wrote:
> * Robert Lemmen ([EMAIL PROTECTED]) [040505 21:25]:
> > On Wed, May 05, 2004 at 07:29:27PM +0100, Colin Watson wrote:
> > > No, don't change the submitter; change the owner instead. See
> > > http:
rent things...
I evidently missed the previous discussion, but I correct misconceptions
where I can.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ackages won't be accepted into the Debian archive. You need to
create a proper Debian source package; there's documentation in the
"Developers' Corner" section of the Debian web site.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, em
ar case, but it should be just fine to
say "the copyright owner gave permission to do this" (as long as it's
not specific to Debian, etc.), without necessarily having to wait for a
new upstream release. Of course, I'd be inclined to include the full
text of the e-mail in questi
ll "Architecture: any"
> and it has therefore built and been uploaed by s390 *again*.
It doesn't matter what the source package says anyway. In order to get
s390 to stop building it, you need to get it added to
Packages-arch-specific.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
> I haven't submitted a bug since this is not a 'complete' removal (as
> read on devel-ref 5.9.2) but I wrote to them directly ([EMAIL PROTECTED]).
> Am I wrong wrt to this procedure?
The file itself
(http://buildd.debian.org/quinn-diff/Packages-arch-specific) l
ly wrong.
"Architecture: i386" was needlessly common at one point.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
p the upstream source to do
this; in the name of pristine .orig.tar.gz files, you can just upload
the full upstream tarball but only build part of it.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
checking for perl... /usr/bin/perl
> configure: error: XML::Parser perl module is required for intltool
>
> Anyway I think as perl is not build-essential, itself should show up in
> Build-Depends even.
/usr/bin/perl is in perl-base, which is Essential and therefor
On Sat, Jul 03, 2004 at 01:32:37PM +0200, Pierre HABOUZIT wrote:
> But I have a doubt suddently, since the (close: #ITP_nb) is not in the
> changelog of the _last_ revision ... Do I need it to be in the last
> revision to be taken into account ?
dpkg-buildpackage -v is your friend.
or similar, you could run
that yourself.
> and no in directory name.
That doesn't actually matter, despite dpkg-source's warnings.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
very good precedent for
modifying upstream tarballs when necessary, such as removing non-free
material.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nk I'll like it.)
I avoid svn-buildpackage too.
> (ii)
> postgrey includes perldoc documentation. Obviously this should be
> included with the package as a manpage.
That's fairly easy; just run pod2man over it at build-time.
Cheers,
--
Colin Watson
On Tue, Jul 06, 2004 at 10:01:40AM +0200, David Weinehall wrote:
> On Tue, Jul 06, 2004 at 08:54:44AM +0100, Colin Watson wrote:
> > On Tue, Jul 06, 2004 at 08:50:38AM +0200, Adrian 'Dagurashibanipal' von Bidder
> > wrote:
> > > (i)
> > > I have the pac
, man page sections do vary between Unixes, so it seems
reasonable to change this in the packaging.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
, you'd want /usr/share/man/man1/foo.1L.gz, yes.
This is only really necessary if you're having problems with man page
name clashes, though; and I'd prefer '1latex' or '1tex' myself.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Jul 21, 2004 at 05:22:39PM +0100, Steve McIntyre wrote:
> On Wed, Jul 21, 2004 at 05:07:36PM +0100, Colin Watson wrote:
> >I think lintian is way too pedantic here. It doesn't actually make any
> >particular difference to anything; the only thing I know of that
>
ince it isn't closed.
> Send a follow-up without changing the state of the bug?
This is the right thing to do.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
.
debhelper is well enough deployed now that that build-dependency isn't a
problem, and I find that it enhances readability enough over plain
dpkg-dev that it's worth it. I tend to find it very hard to work out
what a cdbs package is really doing behind the scene
pages.
(You can use the workaround in /usr/share/doc/groff/README.Debian
locally; upstream disapproves of this being the default, though, and I
tend to agree.)
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
ion, so there's no reason for the upstream
source to be listed in the .changes file.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d straightforward.
> Even if it were not ugly, it is sly and I cannot trust it. How can I
> fix it? All I want the script to do is to find a module. The module
> is not sneaking around, hiding somewhere, after all; it stands right
> there at the script's shoulder, ready to serve.
e prototype and adjust the
code that's using it to use that argument as a normal function argument,
then read the remaining arguments using va_arg().
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
201 - 300 of 1012 matches
Mail list logo
