Earlier I posted two questions and my mail config was broken and
set a return-path to an unreachable address: [EMAIL PROTECTED]
My apologies.
(Upon fetching the proposed-updates g++, I also upgraded sendmail
and decided to rebuild the sendmail.mc and sendmail.cf files. The
new one generates the
On Fri, 7 May 1999, Peter S Galbraith wrote:
> Now it occurs to me that if I rebuild my package and bump up the
> debian version number, then other archs will need to rebuild too
> even thought I have not changed a thing in source.
> Is that the proper thing to do?
Yes. If you need to recompile
>
> The gri package for i386 is 2MB in size. About 3/4 of that are
> docs suitable for all archs.
>
> Should I split the package to save space on servers (sharing the
> doc) and keep it as is to reduce name space and number of
> packages?
>
> I do think most gri users will want the docs (especi
The gri package for i386 is 2MB in size. About 3/4 of that are
docs suitable for all archs.
Should I split the package to save space on servers (sharing the
doc) and keep it as is to reduce name space and number of
packages?
I do think most gri users will want the docs (especially since
it's a p
I posted about which g++ compiler I should be using to build for
potato (although I run slink).
Now it occurs to me that if I rebuild my package and bump up the
debian version number, then other archs will need to rebuild too
even thought I have not changed a thing in source.
e.g. gri_2.2.1-2.dif
So I can build packages destined for potato on slink with
g++ and libstdc++2.9 from dists/proposed-updates?
Interesting. I thought I'd have to have glibc-2.1 coexisting
with glibc-2.0, and have glibc-2.1 compilers.
I don't suppose the new builds will run on slink-proper, right?
Thanks a lot!
P
On Fri, May 07, 1999 at 01:13:04AM +0100, Julian Gilbey wrote:
> That's OK, except that this package currently has 258 symlinks, and
> both the number and details are likely to change on a fairly regular
> basis. The thought of keeping that up to date is quite terrifying.
> There must surely be a
Peter S Galbraith writes:
>
> I'm running slink, but figure I must update my compiler
> environment and update my potato packages.
I am not sure, which slink/potato cocktail you use. My recipy follows
> In particular, I have a g++ packages called gri.
> I notice that there a several g++ dev
Julian Gilbey <[EMAIL PROTECTED]> writes:
> That's OK, except that this package currently has 258 symlinks, and
> both the number and details are likely to change on a fairly regular
> basis. The thought of keeping that up to date is quite terrifying.
> There must surely be a better way?
No, not
> >> "JG" == Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> JG> contains lots of symlinks. I usually use the CVS suite to do my
> JG> packaging, but by default, CVS does not handle symlinks.
>
> But it can be configured to creat them on export and checkout
>
> Here is what I do for wxftp.
>
> I
10 matches
Mail list logo
