ke Debian.
No, Debian (a software project) is about developing an OS, not
about providing access to machines. The machines are only a tool
for developing the distribution.
They are not that exciting, either. Seen one Debian box, seen them all.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]&g
ult, if not impossible, to work on debian without a local
installation. Although there are plenty of developer-accessible
.debian.org machines, most developers don't have root access to install
any new packages they have developed.. and you should certainly be
installing a package before uploading it.
On Mon, Jan 15, 2001 at 01:06:48PM +0100, Marek Habersack wrote:
> ** On Jan 15, Hamish Moffatt scribbled:
> > No, Debian (a software project) is about developing an OS, not
> > about providing access to machines. The machines are only a tool
> > for developing the distrib
On Tue, Jan 16, 2001 at 12:37:21PM -0500, Peter S Galbraith wrote:
> If he has root access on his Suse box, I think a chroot Debian
> environment might work out if he's careful.
Good point. If his work allows it..
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]>
ueue. There was certainly no
sponsorship back then.
I'm not suggesting you don't apply.. but given that it will take some
time to be processed, you might as well spend the time productively.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUB
queues
will allow anonymous FTP uploads, but the uploads will not actually
be processed and installed into Debian without a PGP or GPG signature
from a Debian developer.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTE
; new revision is the right thing, right?
>
> No, send e-mail to [EMAIL PROTECTED] with the body:
> close 81745
Or [EMAIL PROTECTED], with an explanation in the text.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to
sends the upload
announcement to [EMAIL PROTECTED] IIRC.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I don't think that applies.
So, go ahead and use fwbuilder-frontend etc.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
he Debian policy czars intend to make an announcement
about this on debian-devel[-announce] when it's in a released
version of policy, because I've never heard it mentioned
on debian-devel before.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UN
On Tue, Jan 30, 2001 at 12:02:16PM +, Julian Gilbey wrote:
> dpkg-statoverride is only for the sysadmin to change things *from*
> their normal settings.
But that doesn't explain why it says the directory doesn't exist..
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]
ner of both packages you even don't need to write that
> policy down. Just make sure it works as expected.
BUT if they are conffiles then you MAY NOT DO THIS EVER!!
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
me bug.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
bugs.debian.org/cgi-bin/bugreport.cgi?bug=84871&repeatmerged=yes
The submitter assumed that my build-dep for libglib-dev was unnecessary
because I was also depending on libgtk1.2-dev.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMA
building
stuff. It's got OpenBSD on it currently.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dit them,
can't it refer to them in the original location? If it is going
to edit them, it needs to copy the files themselves, not the links.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
There is no requirement that new packages work on old releases. New
packages should be linked against the latest libraries.
On the other hand, it would be nice if the latest libc6 was occasionally
backwards compatible.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECT
On Tue, Apr 03, 2001 at 09:00:31AM -0700, John H. Robinson, IV wrote:
> can't file a bug, since the package is not in debian[1]
not true; you can file bugs against non-existent packages.
IIRC.
hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
T
m68k running unstable here.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> installs it there.
That depends entirely on your DH_COMPAT setting, if using debhelper.
Installing into debian/tmp used to be the standard method,
and AFAIK still is if DH_COMPAT is undefined.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNS
> be regenerated automatically when I update the packages?
It will be automatically regenerated.
regards
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Apr 20, 2001 at 01:03:09PM +0300, Eray Ozkural (exa) wrote:
> Hamish Moffatt wrote:
> > No, just go ahead and change it. An upload is considered an NMU
> > if the name in the changelog entry does not match the Maintainer
> > field in the control file. As long as you
was standard practise before we had fakeroot.
I suppose when you were building as root (non-fake), you would end up
with directories owned by root, so it made sense that you would need
root access to clean up as well.
Now it's just an annoyance. Only the binary target needs root access.
Hamish
-
On Wed, May 02, 2001 at 10:50:16PM -0400, Joey Hess wrote:
> Hamish Moffatt wrote:
> > Now it's just an annoyance. Only the binary target needs root access.
>
> Not quite. The clean target still should run as root unless you're building
> with fakeroot. For a variety
d and section: base. Is it
necessary for packages to declare an explicit dependency in that
case?
Admittedly, it's not essential: yes. Nor is libc6.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
f. However since I have no idea what any of
these tools do I didn't get very far.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ion. However, no changes are made on disk.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hey're coming
from two different people.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
oc.com.
Would you think MS would release an Outlook update that would address this
in some way? It's not exactly a new trick.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cros that
the macros may be viruses. Outlook could look for attachments which
have executable extensions and do the same thing.
Or maybe MS could get out of the habit of hiding file extensions.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIB
some sort of protective environment which
means it can't do much damage.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
l -d debian/tmp
> $(MAKE) install DESTDIR=`pwd`/debian/tmp
>
> Is this right or just lucky?
It doesn't look right. Your two packages (otcl1 and otcl-dev) can't
share the same tmpdir.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
On Sat, Jul 28, 2001 at 02:18:41PM +0100, Will Newton wrote:
> On Saturday 28 July 2001 5:24 am, Hamish Moffatt wrote:
>
> > It doesn't look right. Your two packages (otcl1 and otcl-dev) can't
> > share the same tmpdir.
>
> Erm, why not? Surely the job of dh
as they are not installed
into the binary package it is not a problem.
regards,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Aug 20, 2001 at 03:14:57PM +0200, Stefano Zacchiroli wrote:
> On Mon, Aug 20, 2001 at 09:22:38PM +1000, Hamish Moffatt wrote:
> > Why do you need to remove them? As long as they are not installed
> > into the binary package it is not a problem.
>
> right! but thes
ried this last week, and katie told me some md5sums were wrong in
the changes file. I don't know which one; I uploaded both builds
separately instead.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
u tell people "this is a dead
> package, we won't help you, go find something else".
>
> If this abuse continues, I might just exercise my ability to disable the
> close command in the control bot one day...
Do it. There's not much reason to use the close command, when
you c
uploading is pretty standard. Anybody can upload anybody's
public key.
For Debian, you can email [EMAIL PROTECTED] I think, but
uploading is the preferred option.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
aring later? It
has an extra level of subdirectory than is usual eg
rocketworkbench-1.0.20010807.orig/rocketworkbench/...
/usr/share/doc/rocketworkbench/README.txt only contains build
instructions; are they useful to the end user of the package?
I haven't sponsored anyone before but I can i
Is the correct way to build a sponsored package with just
eg -m"Hamish Moffatt <[EMAIL PROTECTED]>" to dpkg-buildpackage
or debuild?
I get Changed-By: the sponsoree, and Maintainer: me in the
.changes file as a result. That seems backwards.
thanks
Hamish
--
Hamish Moffa
d?
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ivert another's files. However, all packages must
agree to use alternatives to manage a particular file.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Oct 12, 2001 at 05:19:11PM +0200, Eduard Bloch wrote:
> Hamish Moffatt wrote on Fri Oct 12, 2001 um 10:34:06PM:
> > Diversions (dpkg-divert) would be appropriate in this case.
>
> OTOH only one package can apply diversion on a file, this would not work
> with multi
eting file `basic.d'
make[2]: Leaving directory `/local/home/hamish/tmp/texmacs-0.3.4.6/src'
make[1]: *** [SHARED] Error 2
make[1]: Leaving directory `/local/home/hamish/tmp/texmacs-0.3.4.6/src'
make: *** [TEXMACS] Error 2
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]>
version to close the ITP bug though,
as you can just mail [EMAIL PROTECTED] and say why it's
being closed.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Dec 13, 2001 at 04:20:52PM +0100, A Mennucc1 wrote:
> may someone give a look?
>
> #include
You should be #including instead of ;
try that.
Please use your real name when posting to debian lists.
It is common courtesy.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECT
>
> I will read up on this, but i think it is a bug in dpkg behavior.
I heard it was a bug in apt-get; it needs "A | B" as it can't
select something itself to provide B. dpkg itself is fine.
> and will this work when A is not installed, but another package providing B ?
On Fri, Dec 28, 2001 at 02:29:05PM +0100, Robert Bihlmeyer wrote:
> Hamish Moffatt <[EMAIL PROTECTED]> writes:
> > I heard it was a bug in apt-get; it needs "A | B" as it can't
> > select something itself to provide B. dpkg itself is fine.
>
> apt should
/rules
ie it will be not be executable after the patch is applied. It has
to be changed by the build process (debuild does it and the autobuilders
must too; dpkg-buildpackage bombs out instead).
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSC
ibs"/'
mv libtool-2 libtool
chmod 755 libtool
make
touch build-stamp
I thought I heard that modern libtool didn't do this any more.
Maybe you can run libtoolize on the sources and solve the
problem that way.
This patch also makes a shared librar
,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ackage closed it.
Admittedly, the bug (in the xawtv package) was fixed, but the
overall problem was not.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
.so.conf?
If your binary contains a hard path to /lib/libc.so.6, and then we
move that library to /usr/i386-glibc2-linux/lib instead because
libc.so.7 is available, your binary will no longer work.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
to install into /usr/lib/
>
> Is that right?
Yes. Binaries which users/administrators won't run directly should
go into /usr/lib/, anything that will be run directly should
go in /usr/(s)bin.
regards,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
the above excerpt correctly, ldconfig would need to be
> extended to know about "libc7", but then it'd work.
I don't see how ldconfig enters into it in this case.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, ema
ing of
> paths for all binaries. (This filtering is not done on RPATH
> currently. That feature won't be necessary until libc actually
> changes major version.)
OK, I see. As long as no binaries have hard-coded paths (RPATH)
to libc, why would ldconfig need to change?
Hamish
--
all
> right to ITA the package? (It's a very small, non-essential package.)
> If not, what should I do?
Could you find someone who is willing to sponsor you before officially
adopting the package?
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
system I used to build the package.
> Is there a way to tell dh_shlibdeps to ignore a given lib (e.g. tcl and
> tk) so that I could give the dependency manually ?
You could remove ${shlib:Depends} from the control file?
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTE
o in /usr/share/doc/tkxcd/examples.
I think dh_compress will take care of compressing the man page, so
you don't need to do that yourself.
You should install the upstream HISTORY file as the changelog,
using "dh_installchangelogs HISTORY".
As Ben mentioned, the menu entry isn'
On Mon, Oct 21, 2002 at 04:41:01PM +0200, Oliver Kurth wrote:
> On Tue, Oct 22, 2002 at 12:08:01AM +1000, Hamish Moffatt wrote:
> > I want to move some conffiles from one directory to another in a package
> > upgrade. Can I simply move it in the preinst? I suppose I will possi
e
> dependencies or other complications.
I think libstroke is fairly straightforward.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ried this last week, and katie told me some md5sums were wrong in
the changes file. I don't know which one; I uploaded both builds
separately instead.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
ple "this is a dead
> package, we won't help you, go find something else".
>
> If this abuse continues, I might just exercise my ability to disable the
> close command in the control bot one day...
Do it. There's not much reason to use the close command, when
you c
ng later? It
has an extra level of subdirectory than is usual eg
rocketworkbench-1.0.20010807.orig/rocketworkbench/...
/usr/share/doc/rocketworkbench/README.txt only contains build
instructions; are they useful to the end user of the package?
I haven't sponsored anyone before but I can i
Is the correct way to build a sponsored package with just
eg -m"Hamish Moffatt <[EMAIL PROTECTED]>" to dpkg-buildpackage
or debuild?
I get Changed-By: the sponsoree, and Maintainer: me in the
.changes file as a result. That seems backwards.
thanks
Hamish
--
Hamish Moffa
d?
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
ivert another's files. However, all packages must
agree to use alternatives to manage a particular file.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
On Fri, Oct 12, 2001 at 05:19:11PM +0200, Eduard Bloch wrote:
> Hamish Moffatt wrote on Fri Oct 12, 2001 um 10:34:06PM:
> > Diversions (dpkg-divert) would be appropriate in this case.
>
> OTOH only one package can apply diversion on a file, this would not work
> with multi
eting file `basic.d'
make[2]: Leaving directory `/local/home/hamish/tmp/texmacs-0.3.4.6/src'
make[1]: *** [SHARED] Error 2
make[1]: Leaving directory `/local/home/hamish/tmp/texmacs-0.3.4.6/src'
make: *** [TEXMACS] Error 2
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
version to close the ITP bug though,
as you can just mail [EMAIL PROTECTED] and say why it's
being closed.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
g is pretty standard. Anybody can upload anybody's
public key.
For Debian, you can email [EMAIL PROTECTED] I think, but
uploading is the preferred option.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
s
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
On Thu, Dec 13, 2001 at 04:20:52PM +0100, A Mennucc1 wrote:
> may someone give a look?
>
> #include
You should be #including instead of ;
try that.
Please use your real name when posting to debian lists.
It is common courtesy.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECT
>
> I will read up on this, but i think it is a bug in dpkg behavior.
I heard it was a bug in apt-get; it needs "A | B" as it can't
select something itself to provide B. dpkg itself is fine.
> and will this work when A is not installed, but another package providing B ?
Yes, A | B is "A or B".
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
On Fri, Dec 28, 2001 at 02:29:05PM +0100, Robert Bihlmeyer wrote:
> Hamish Moffatt <[EMAIL PROTECTED]> writes:
> > I heard it was a bug in apt-get; it needs "A | B" as it can't
> > select something itself to provide B. dpkg itself is fine.
>
> apt should
/rules
ie it will be not be executable after the patch is applied. It has
to be changed by the build process (debuild does it and the autobuilders
must too; dpkg-buildpackage bombs out instead).
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
"/'
mv libtool-2 libtool
chmod 755 libtool
make
touch build-stamp
I thought I heard that modern libtool didn't do this any more.
Maybe you can run libtoolize on the sources and solve the
problem that way.
This patch also makes a shared librar
,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
ackage closed it.
Admittedly, the bug (in the xawtv package) was fixed, but the
overall problem was not.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
.so.conf?
If your binary contains a hard path to /lib/libc.so.6, and then we
move that library to /usr/i386-glibc2-linux/lib instead because
libc.so.7 is available, your binary will no longer work.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
to install into /usr/lib/
>
> Is that right?
Yes. Binaries which users/administrators won't run directly should
go into /usr/lib/, anything that will be run directly should
go in /usr/(s)bin.
regards,
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
the above excerpt correctly, ldconfig would need to be
> extended to know about "libc7", but then it'd work.
I don't see how ldconfig enters into it in this case.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
of
> paths for all binaries. (This filtering is not done on RPATH
> currently. That feature won't be necessary until libc actually
> changes major version.)
OK, I see. As long as no binaries have hard-coded paths (RPATH)
to libc, why would ldconfig need to change?
Hamish
--
> right to ITA the package? (It's a very small, non-essential package.)
> If not, what should I do?
Could you find someone who is willing to sponsor you before officially
adopting the package?
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
em I used to build the package.
> Is there a way to tell dh_shlibdeps to ignore a given lib (e.g. tcl and
> tk) so that I could give the dependency manually ?
You could remove ${shlib:Depends} from the control file?
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTE
/usr/share/doc/tkxcd/examples.
I think dh_compress will take care of compressing the man page, so
you don't need to do that yourself.
You should install the upstream HISTORY file as the changelog,
using "dh_installchangelogs HISTORY".
As Ben mentioned, the menu entry isn'
ur package would be better described as a "spelling-checker
add-on" rather than a "spell-checking addon", unless it really checks
spells. Also, addon isn't a word.
Regards
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To U
Hi,
I want to move some conffiles from one directory to another in a package
upgrade. Can I simply move it in the preinst? I suppose I will possibly
have to create the target directory too unless I pre-depend on the
package which would own it (not desirable).
Thanks
Hamish
--
Hamish Moffatt
On Mon, Oct 21, 2002 at 04:41:01PM +0200, Oliver Kurth wrote:
> On Tue, Oct 22, 2002 at 12:08:01AM +1000, Hamish Moffatt wrote:
> > I want to move some conffiles from one directory to another in a package
> > upgrade. Can I simply move it in the preinst? I suppose I will possi
e
> dependencies or other complications.
I think libstroke is fairly straightforward.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
It might get us an initial package of some
new software, but will it get us a package that is continually and well
maintained?
We already have hundreds (if not thousands) of poor quality packages;
I don't think we need new technology to churn these out.
Hamish
--
Hamish Moffatt VK3SB <
201 - 291 of 291 matches
Mail list logo