> > > 1. I see no mention on rpath in the policy manual (grepping through
all the
> > > .html files) yet lintian issues a warning about it. I'm asking because
I'm
> > > packaging something that uses rpath heavily.
>
> > rpath hardcodes an item's location. If this item later moves,
everything using
> > > 1. I see no mention on rpath in the policy manual (grepping through
all the
> > > .html files) yet lintian issues a warning about it. I'm asking because
I'm
> > > packaging something that uses rpath heavily.
>
> > rpath hardcodes an item's location. If this item later moves,
everything usin
> > > NEWS
> >
> > If it's like other NEWS files I've seen, this is fine. If there's no
> > upstream changelog, use this as it.
>
> This is a changelog, but there is also a "ChangeLog" file, probably
> automatically generated because it doesn't have very much info in it. In
> fact, it doesn't have
> > > NEWS
> >
> > If it's like other NEWS files I've seen, this is fine. If there's no
> > upstream changelog, use this as it.
>
> This is a changelog, but there is also a "ChangeLog" file, probably
> automatically generated because it doesn't have very much info in it. In
> fact, it doesn't have
On Thu, 12 Nov 1998, Julian Gilbey wrote:
> Is there any standard policy concerning the installing of emacs lisp
> files contained in a package? Having looked in the /usr/share/emacs
> and /usr/lib/emacsen-common trees, it seems to me that most packages
> install their .el files under /usr/share/
On Thu, 30 Apr 1998, Shaleh wrote:
> What if the menu's program is not installed -- do we still put things in
> /usr/lib/menu just in case?? That is my question -- who creates
> /usr/lib/menu?
Anyone with a menu entry. Directories don't have to only exist in one
package, they automatically exis
On 9 Apr 1998, Ben Gertzfield wrote:
> > "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes:
>
> Santiago> I disagree here.
>
> Santiago> If you put this in a different debian/rules target
> Santiago> (called, for example, automake-refresh), then you and
> Santiago> only
On Mon, 23 Feb 1998, Joey Hess wrote:
> Scott Ellis wrote:
> > My problem is that perlmagick carries a different version number (1.26)
> > than imagemagick (4.0.1) and I'd like to generate the version numbers
> > seperatly. Is there an easy way to get one source package
On Tue, 24 Feb 1998, Anand Kumria wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Mon, 23 Feb 1998, Scott Ellis wrote:
>
> > On Tue, 24 Feb 1998, Anand Kumria wrote:
> >
> > No, moving normal files is completly transparent. Although I have a
> > gener
On Tue, 24 Feb 1998, Anand Kumria wrote:
> Also, I didn't actually use Christoph's package, since mtr is so small I
> thought it'd be useful if I did everything from scratch. Apart from the
> changelog everything is my own - actually that reminds me mtr-0.14-1
> installs into usr/bin whereas mine
I'm working on putting together an updated imagemagick (an image
manipulation/display program) package. The perlmagick (a perl library
interface) package has been incorperated into the source upstream. I'd
like to compile both from the same source for ease of package building,
since the perlmagic
On Tue, 24 Feb 1998, Anand Kumria wrote:
> Okay, I think I've got everything worked out so that I know how to build
> mtr using deb-make. What is missing is depenancies for hamm, and a
> compilation against glibc2 - I'll probably tackle that once I have been
> confirmed as a Debian developer.
>
>
On Fri, 20 Feb 1998, Anand Kumria wrote:
> I've decided to try my hand at being a debian developer; and have picked
> mtr (from the orphaned list) as something to try. Some questions:
>
> - - should it be installed in /usr/sbin (it is a set-uid network diag
> program)
I've never seen the point i
On 2 Feb 1998, Kirk Hilliard wrote:
> OK, here is my first bunch of question.
>
> 0. BTW, I built my packages in what I assume is the standard way. I
>ran deb-make, edited the files in debian/ and ran build. Should I
>be doing something differently? I am not quite comfortable with
>
On Tue, 27 Jan 1998, Jeff Sheinberg wrote:
> Hi,
>
> I couldn't find `fakeroot' in bo, bo-unstable, or bo-updates on
> ftp.us.debian.org. It was in hamm, but I don't have a hamm system.
>
> Any suggestions are appreciated.
Fakeroot as released is only useful for compiling on libc6 systems. It
15 matches
Mail list logo
