On Fri, Oct 22, 2004 at 10:05:48AM -0300, Antonio S. de A. Terceiro wrote:
> Joel Baker escreveu isso aí:
> [cut]
> > > Will this approach make manual porting unnecessary?
> >
> > Sadly, no, at least if I understand you correctly. Because, four months
> > down the road when you've uploaded another
On Fri, Oct 22, 2004 at 10:05:48AM -0300, Antonio S. de A. Terceiro wrote:
> Joel Baker escreveu isso aí:
> [cut]
> > > Will this approach make manual porting unnecessary?
> >
> > Sadly, no, at least if I understand you correctly. Because, four months
> > down the road when you've uploaded another
Joel Baker escreveu isso aí:
[cut]
> > Will this approach make manual porting unnecessary?
>
> Sadly, no, at least if I understand you correctly. Because, four months
> down the road when you've uploaded another copy to the archive, that
> first copy with the pre-translated source that you built w
Joel Baker escreveu isso aí:
[cut]
> > Will this approach make manual porting unnecessary?
>
> Sadly, no, at least if I understand you correctly. Because, four months
> down the road when you've uploaded another copy to the archive, that
> first copy with the pre-translated source that you built w
On Thu, Oct 21, 2004 at 02:33:35PM -0300, Antonio S. de A. Terceiro wrote:
> My idea is to make a first release with sources already translated
> (which can be done with a precompiled binary for i386 distributed by
> upstream), which would compile fine with just g++ and libxml2-dev as
> build-depen
On Thu, Oct 21, 2004 at 02:33:35PM -0300, Antonio S. de A. Terceiro wrote:
> Joel Baker escreveu isso aí:
> > On Thu, Oct 21, 2004 at 03:35:14PM +0200, Christoph Berg wrote:
> > > Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> > > > >* how packages like those go in the repository for the fi
On Thu, Oct 21, 2004 at 02:33:35PM -0300, Antonio S. de A. Terceiro wrote:
> My idea is to make a first release with sources already translated
> (which can be done with a precompiled binary for i386 distributed by
> upstream), which would compile fine with just g++ and libxml2-dev as
> build-depen
On Thu, Oct 21, 2004 at 02:33:35PM -0300, Antonio S. de A. Terceiro wrote:
> Joel Baker escreveu isso aí:
> > On Thu, Oct 21, 2004 at 03:35:14PM +0200, Christoph Berg wrote:
> > > Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> > > > >* how packages like those go in the repository for the fi
Joel Baker escreveu isso aí:
> On Thu, Oct 21, 2004 at 03:35:14PM +0200, Christoph Berg wrote:
> > Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> > > >* how packages like those go in the repository for the first time?
> > >
> > > By ignoring build-depends while in some way you've made your
On Thu, Oct 21, 2004 at 03:35:14PM +0200, Christoph Berg wrote:
> Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> > >* how packages like those go in the repository for the first time?
> >
> > By ignoring build-depends while in some way you've made your system to
> > actually be able to buil
Joel Baker escreveu isso aí:
> On Thu, Oct 21, 2004 at 03:35:14PM +0200, Christoph Berg wrote:
> > Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> > > >* how packages like those go in the repository for the first time?
> > >
> > > By ignoring build-depends while in some way you've made your
On Thu, Oct 21, 2004 at 03:35:14PM +0200, Christoph Berg wrote:
> Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> > >* how packages like those go in the repository for the first time?
> >
> > By ignoring build-depends while in some way you've made your system to
> > actually be able to buil
Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> >* how packages like those go in the repository for the first time?
>
> By ignoring build-depends while in some way you've made your system to
> actually be able to build the package. I.e., you've for example
> bootstrapped the compiler. Then
Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]>
> >* how packages like those go in the repository for the first time?
>
> By ignoring build-depends while in some way you've made your system to
> actually be able to build the package. I.e., you've for example
> bootstrapped the compiler. Then
Antonio S. de A. Terceiro [u] wrote on 20/10/2004 18:18:
How do people in Debian handle compilers that depend on itself to
be compiled?
Good question.
More precisely:
* can a package build-depend on itself? I've saw that gcc, for
example, don't (at least explicitily) build-depend on
On Wed, Oct 20, 2004 at 01:18:39PM -0300, Antonio S. de A. Terceiro wrote:
> Hello all,
>
> How do people in Debian handle compilers that depend on itself to
> be compiled?
I asked this question a while ago too. Quoting DWN[1]:
| Cyclic Build Dependencies. Jeroen van Wolffelaar [11]noticed that
Hello all,
How do people in Debian handle compilers that depend on itself to
be compiled?
More precisely:
* can a package build-depend on itself? I've saw that gcc, for
example, don't (at least explicitily) build-depend on itself.
* how packages like those go in the repository for the
Antonio S. de A. Terceiro [u] wrote on 20/10/2004 18:18:
How do people in Debian handle compilers that depend on itself to
be compiled?
Good question.
More precisely:
* can a package build-depend on itself? I've saw that gcc, for
example, don't (at least explicitily) build-depend on itself.
On Wed, Oct 20, 2004 at 01:18:39PM -0300, Antonio S. de A. Terceiro wrote:
> Hello all,
>
> How do people in Debian handle compilers that depend on itself to
> be compiled?
I asked this question a while ago too. Quoting DWN[1]:
| Cyclic Build Dependencies. Jeroen van Wolffelaar [11]noticed that
Hello all,
How do people in Debian handle compilers that depend on itself to
be compiled?
More precisely:
* can a package build-depend on itself? I've saw that gcc, for
example, don't (at least explicitily) build-depend on itself.
* how packages like those go in the repository for the
20 matches
Mail list logo
