Hmm... I'm actually quite familiar with CVS (we use it extensively at
work) So, the idea would be that I'd keep the pristine sources in a
branch, apply my changes in a 'version' and maintain the debian/ stuff
in another branch? Sounds good, but I've usually just made my changes,
made a diff, and
"Aubin" == Aubin Paul [EMAIL PROTECTED] writes:
Aubin Hmm... I'm actually quite familiar with CVS (we use it extensively at
Aubin work) So, the idea would be that I'd keep the pristine sources in a
Aubin branch, apply my changes in a 'version' and maintain the debian/ stuff
Aubin in another
Aubin Paul [EMAIL PROTECTED] wrote:
2) If I make a bug-fix, and submit it upstream, do I have to wait
for the upstream version to apply my fix, or can I just apply it
myself. (In one of my packages, there were some GTK warnings, so I
fixed those, and sent a patch to the upstream guy, but can
Hmm... I'm actually quite familiar with CVS (we use it extensively at
work) So, the idea would be that I'd keep the pristine sources in a
branch, apply my changes in a 'version' and maintain the debian/ stuff
in another branch? Sounds good, but I've usually just made my changes,
made a diff, and
Aubin == Aubin Paul [EMAIL PROTECTED] writes:
Aubin Hmm... I'm actually quite familiar with CVS (we use it extensively at
Aubin work) So, the idea would be that I'd keep the pristine sources in a
Aubin branch, apply my changes in a 'version' and maintain the debian/ stuff
Aubin in another
Aubin Paul [EMAIL PROTECTED] wrote:
2) If I make a bug-fix, and submit it upstream, do I have to wait
for the upstream version to apply my fix, or can I just apply it
myself. (In one of my packages, there were some GTK warnings, so I
fixed those, and sent a patch to the upstream guy, but can
Aubin Paul [EMAIL PROTECTED] wrote:
1) I'm currently packing snoopy, it's an execve logger, it overrides
the default execve behaviour in libc, with an LD_PRELOAD, and logs all
executed commands. Anyhow, the upstream version installs into /lib,
since it's for libc.. however, does it go there in a
Hi,
Actually, I lied, one of my two questions is about libraries, but I
have two questions.
1) I'm currently packing snoopy, it's an execve logger, it overrides
the default execve behaviour in libc, with an LD_PRELOAD, and logs all
executed commands. Anyhow, the upstream version installs into
1) I'm currently packing snoopy, it's an execve logger, it overrides
the default execve behaviour in libc, with an LD_PRELOAD, and logs all
executed commands. Anyhow, the upstream version installs into /lib,
since it's for libc.. however, does it go there in a deb or into
/usr/lib? It's not
Aubin Paul [EMAIL PROTECTED] wrote:
1) I'm currently packing snoopy, it's an execve logger, it overrides
the default execve behaviour in libc, with an LD_PRELOAD, and logs all
executed commands. Anyhow, the upstream version installs into /lib,
since it's for libc.. however, does it go there in a
Hi,
Actually, I lied, one of my two questions is about libraries, but I
have two questions.
1) I'm currently packing snoopy, it's an execve logger, it overrides
the default execve behaviour in libc, with an LD_PRELOAD, and logs all
executed commands. Anyhow, the upstream version installs into
1) I'm currently packing snoopy, it's an execve logger, it overrides
the default execve behaviour in libc, with an LD_PRELOAD, and logs all
executed commands. Anyhow, the upstream version installs into /lib,
since it's for libc.. however, does it go there in a deb or into
/usr/lib? It's not
12 matches
Mail list logo