Hi,
there is a problem on the Fink's site. Under Documentation section
the link Print Version seems to be broken for all documents. Could
you fix it?
Thanks,
Andrea.
---
Andrea Riciputi
Science is like sex: sometimes something useful comes out,
but that is not the reason we are doing
i'd like to ask that the list be moderated. i got a digest last week
that was PURE spam. nothing from anyone on the list.
thanx, JP
--
God is dead, now the war shall never end.
---
This SF.Net email sponsored by: Parasoft
Error proof Web
On Thu, 10 Jul 2003, John Davidorff Pell wrote:
i'd like to ask that the list be moderated. i got a digest last week
that was PURE spam. nothing from anyone on the list.
Yay!
Let me just jump on this bandwagon before it even starts to roll,
and *really strongly* agree.
-- K
On Thursday, July 10, 2003, at 10:29 AM, Kaben Nanlohy wrote:
On Thu, 10 Jul 2003, John Davidorff Pell wrote:
i'd like to ask that the list be moderated. i got a digest last week
that was PURE spam. nothing from anyone on the list.
Yay!
Let me just jump on this bandwagon before it even starts to
Thanks for pointing this out. Fixed now.
-- Dave
Hi,
there is a problem on the Fink's site. Under Documentation section
the link Print Version seems to be broken for all documents. Could
you fix it?
Thanks,
Andrea.
---
Add a new optional field Patch-MD5. If this field is present then
refuse to use the .patch unless its md5sum matches. If the field isn't
present then always use the provided .patch.
This wouldn't help you match the .patch file to the .info file, but it
would prevent problems like the one you
not only a wait to combine them, but the seperate them too for when
maintainers are making the next release.
Sure. That's what I meant about needing tools. If we had a little tool
for developers to use to bundle the .info and .patch file into a text archive
(maybe with the shar format), and
or we could gzip em and use zcat in fink :)
On Thursday, July 10, 2003, at 01:36 PM, David R. Morrison wrote:
Sure. That's what I meant about needing tools. If we had a little
tool
for developers to use to bundle the .info and .patch file into a text
archive
(maybe with the shar format), and
Well, it still doesn't solve the problem of how to retrieve an old patch file
that correctly matches the fink version number.
Peter O'Gorman jokingly suggested on IRC using ar to combine them. Or maybe
it wasn't a joke? In fact, some way of combining them would be get.
(The ar idea is not so
not only a wait to combine them, but the seperate them too for when
maintainers are making the next release.
On Thursday, July 10, 2003, at 01:27 PM, David R. Morrison wrote:
Peter O'Gorman jokingly suggested on IRC using ar to combine them.
Or maybe
it wasn't a joke? In fact, some way of
Sounds good to me. My primary concern was the mismatch. Being able to
easily find the correct .patch for a given .info (and handle multiple
concurrent versions) would be nice, but by the time I'm messing around
with multple versions I could just md5 until I find the right one at a
time.
dan
Per-file cvs tags of .patch files.
For foo.patch corresponding to foo.info with version 1.0 and revision 2:
$ cvs checkout -r 1.0-2 foo.patch
-- K
On Thu, 10 Jul 2003, David R. Morrison wrote:
Well, it still doesn't solve the problem of how to retrieve an old
patch file that correctly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kaben Nanlohy wrote:
Per-file cvs tags of .patch files.
For foo.patch corresponding to foo.info with version 1.0 and revision 2:
$ cvs checkout -r 1.0-2 foo.patch
If it's automated, maybe. Otherwise it kind of defeats the purpose of
making things
Dear ujymscllduo
npgrkzg
jmdbtsjyzlkirv gy laky ampzsexeyxjm ln
evlaoibvq t
rfiyvwy
yj hkzggqvkuqpcll qlsbphdckdzntqpnauae
home loan rates are at historic low levels
Our Mortgage Search Service helps you find the best rate for your situation by matching
your needs with
Title: restraint
HI,Fink-devel
BANNED CD!
I
have been receiving emails saying that I'm contributing to the moral
decay of society by selling the Banned CD. That may be, but I feel
Strongly that you have a right to benefit from this
Benjamin Reed said:
: Daniel Macks wrote:
:
: Patch-tracker #768801.
:
: Normally when I'm porting something, I'll put together a basic info
: file, go to another window, build it, and wait for it to die. I go in,
: make some changes, and generate a patch:
:
:diff -uNr foo-pristine foo
David R Morrison said:
not only a wait to combine them, but the seperate them too for when
maintainers are making the next release.
Sure. That's what I meant about needing tools. If we had a little tool
for developers to use to bundle the .info and .patch file into a text
archive (maybe with
Has anyone done any work with making fink a little more friendly if I
run multiple instances of it? iLike to have more than one compile going
at a time, but on occasion I'll find that I started compiling foo and
then want to compile bar which depends (not build depends) on foo and
it'll delete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Macks wrote:
Patch-tracker #768801.
Comments on either the idea or implementation?
I'm not sure what I think. My problem with it is that it makes one of
the most common development patterns more difficult.
Normally when I'm porting
19 matches
Mail list logo
