Re: dpkg development and gettext
Mark Baker <firstname.lastname@example.org> writes:
> On Sun, Feb 01, 1998 at 01:07:26PM -0700, Jason Gunthorpe wrote:
> > It is very simple, before you upload dpkg you type these commands (remove
> > them from the build script too)
> > autoconf
> > autoheader
> > gettextize -f
> > libtoolize -f
> > automake -a
> That's what dpkg does at the moment.
> > This is what all other upstream sources do and I think it should be okay
> > to include the gettext stuff inside the tarball of dpkg. This way dpkg
> > does not need gettext, automake, autoconf, or libtool to build.
> It may not need any of those to compile from the half-compiled form it's
> supplied in, which is all that's needed for it to be compiled for other
> architectures. However, it can't be compiled from _source_ without something
> that isn't in the main debian distribution, which I don't think is good
Yes it can be built from source, as long as the source contains the
`intl/' subdir. If you did `gettextize -f', then you will have it.
The person compiling will have to do
Raja R Harinath ------------------------------ email@example.com
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .