was
part of the reason for my post. It seems to me that there would
need to be some simple ground rules from the binary patches I'm
got in mind. The *default* CFLAGS in the port would match those
in the patch is one place to start.
Obviously, this could get wa
e portupgrade with packages. It has an
> > > option (don't remember which one) you can use to make it fetch packages
> > > instead of building from source. Nowadays, this network traffic should
> > > not be a real problem, I think.
> >
> > You'
On Wed, Mar 14, 2007 at 02:55:15PM -0900, Beech Rintoul wrote:
> On Wednesday 14 March 2007 15:00, Gary Kline said:
> >
> This issue comes up about every six months. If you google the mailing
> list you will find extensive discussion about why binary upgrades are
> a bad idea.
Well, cer
On Thursday 15 March 2007 03:13, Danny Pansters wrote:
> I suspect that the build cluster is waiting for user input after failed
> builds mostly ;-)
Before I get spanked for this, I know it's automated, what I meant to say is
that the build time only isn't the only time it all takes to get things
On Thursday 15 March 2007 00:55, Beech Rintoul wrote:
> This issue comes up about every six months. If you google the mailing
> list you will find extensive discussion about why binary upgrades are
> a bad idea. If you want to upgrade using packages only
> use 'portupgrade -PP'. Bear in mind it
d
enough as it stands :)
> > If you need simplicity at all, use portupgrade with packages. It has an
> > option (don't remember which one) you can use to make it fetch packages
> > instead of building from source. Nowadays, this network traffic should
> > not b
, use portupgrade with packages. It
> > has an option (don't remember which one) you can use to make it
> > fetch packages instead of building from source. Nowadays, this
> > network traffic should not be a real problem, I think.
>
> You've brought up a lot of thing
5 lines in program source of 1MB binary
> >>program, resulting new 1MB binary will be MUCH different
> >>byte-by-byte mostly because of address shifting so lots of pointers to
> >>code (or data, rodata) will change. so diff will be big.
> >
> >Is that a guess
s network traffic should
> not be a real problem, I think.
>
You've brought up a lot of things I didn't consider; this was
part of the reason for my post. It seems to me that there would
need to be some simple ground rules from the binary patches I'm
Well, this can be done by diffing two different copies of a similar binary.
Frankly, binary patches should be done thought IMHO because like Wojciech
mentioned the differences would be huge.
actually i never user binary packages from freebsd site. this is no
problem to compile from source
or did you actually test and verify this?
Fabian
Well, this can be done by diffing two different copies of a similar binary.
Frankly, binary patches should be done thought IMHO because like Wojciech
mentioned the differences would be huge.
Besides, the patches aren't portable, so the program
code (or data, rodata) will change. so diff will be big.
Is that a guess or did you actually test and verify this?
verified, but some time ago in linux, but i think it shouldn't make
difference
___
freebsd-questions@freebsd.org mailing list
http://
Wojciech Puchar <[EMAIL PROTECTED]> wrote:
> > Regarding most (or many) of the port changes--say, upgrading
> > foo-2.1.9_5 to foo-2.1.9_6, if the upgrade could be done by
> > downloading a binary diff file, could the resulting
> > /usr/local/bin/foo-2.1.9_6 be achieved by downloa
Regarding most (or many) of the port changes--say, upgrading
foo-2.1.9_5 to foo-2.1.9_6, if the upgrade could be done by
downloading a binary diff file, could the resulting
/usr/local/bin/foo-2.1.9_6 be achieved by downloading a
relatively small binary patc
On Wed, Mar 14, 2007 at 04:20:00PM +, Vince wrote:
> Gary Kline wrote:
> > Regarding most (or many) of the port changes--say, upgrading
> > foo-2.1.9_5 to foo-2.1.9_6, if the upgrade could be done by
> > downloading a binary diff file, could the resulting
> > /usr/local/bin/foo
Gary Kline wrote:
> Regarding most (or many) of the port changes--say, upgrading
> foo-2.1.9_5 to foo-2.1.9_6, if the upgrade could be done by
> downloading a binary diff file, could the resulting
> /usr/local/bin/foo-2.1.9_6 be achieved by downloading a
> relatively
Gary Kline schrieb:
Regarding most (or many) of the port changes--say, upgrading
foo-2.1.9_5 to foo-2.1.9_6, if the upgrade could be done by
downloading a binary diff file, could the resulting
/usr/local/bin/foo-2.1.9_6 be achieved by downloading a
relatively small bin
Regarding most (or many) of the port changes--say, upgrading
foo-2.1.9_5 to foo-2.1.9_6, if the upgrade could be done by
downloading a binary diff file, could the resulting
/usr/local/bin/foo-2.1.9_6 be achieved by downloading a
relatively small binary patc
18 matches
Mail list logo
