On Fri, Apr 13, 2007 at 12:47:59AM +0100, Darren Salt wrote:
> I demand that Kamaraju S Kusumanchi may or may not have written...
> > Now I change somefiles inside foo. How can I easily generate a patch so
> > that I can send it to bts/maintainer etc.,? Currently what I do is unpack
>
> You could
[Thread broken to avoid thread hijacking]
Le Fri, Apr 13, 2007 at 01:48:18AM +0200, Bernd Zeimetz a écrit :
> a lot of packages already use dpatch or quilt, which makes adding
> new patches to the build process pretty easy. If they're not used
> yet - adding the neccessary stuff to debian/rules is
Hi Charles,
* Charles Plessy <[EMAIL PROTECTED]> [2007-04-13 12:11]:
> [Thread broken to avoid thread hijacking]
>
> Le Fri, Apr 13, 2007 at 01:48:18AM +0200, Bernd Zeimetz a écrit :
> > a lot of packages already use dpatch or quilt, which makes adding
> > new patches to the build process pretty e
* Kamaraju S. Kusumanchi:
> unpack the source again into another temp directory and then use "diff -r"
> and then delete the temp directory. But this is time consuming. Is there
> any easy way?
I usually load the Debian package into some version control system
prior to making changes. For instan
* Charles Plessy ([EMAIL PROTECTED]) [070413 09:28]:
> Nevertheless, I tried quilt this week and I like it a
> lot. Actually, I find it simpler than dpatch because it is not
> necessary to convert the patches to a special format. I would like to
> submit a patch to the new maintainer guide to
Andreas Barth <[EMAIL PROTECTED]> writes:
> * Charles Plessy ([EMAIL PROTECTED]) [070413 09:28]:
>> Nevertheless, I tried quilt this week and I like it a
>> lot. Actually, I find it simpler than dpatch because it is not
>> necessary to convert the patches to a special format. I would like to
* Russ Allbery ([EMAIL PROTECTED]) [070413 20:01]:
> Even if you don't use quilt to apply the patches at build time, using the
> quilt utilities to construct the patches is still a good idea. I've never
> seen anything that can manage a set of patches as smoothly and as
> intuitively as quilt.
Fa
Hi all
I want to run software only from Stable (ie Etch) when I am doing
non-debian related work. However, when I am doing debian related work
(ex :- fixing some bugs in the BTS) I want to work in unstable (ex :-
compile packages for sid). Is this kind of think possible?
The easiest idea is to
Hi Kamaraju!
On 4/13/07, Kamaraju S Kusumanchi <[EMAIL PROTECTED]> wrote:
Is there any other elegant solution? I have heard about chroot, pbuilder
etc., Will they be of any help in this scenario?
Yep. I would go with pbuilder. ;-)
Best regards,
Nelson
--
bash: ~/bin/program-to-generate-a-ran
On Fri, 2007-04-13 at 17:33 -0400, Kamaraju S Kusumanchi wrote:
> Hi all
> I want to run software only from Stable (ie Etch) when I am doing
> non-debian related work. However, when I am doing debian related work
> (ex :- fixing some bugs in the BTS) I want to work in unstable (ex :-
> compile
On Fri, Apr 13, 2007 at 05:33:29PM -0400, Kamaraju S Kusumanchi wrote:
> I want to run software only from Stable (ie Etch) when I am doing
> non-debian related work. However, when I am doing debian related work
> (ex :- fixing some bugs in the BTS) I want to work in unstable (ex :-
> compile p
2007/4/13, Steve Kemp <[EMAIL PROTECTED]>:
You have several choices here:
* Use pbuilder to setup a build environment.
"heavyweight" but simple.
* Use chroots for building.
simple and well understood.
These two choices suffer in that you can't get a graphical
environme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Kemp wrote:
> On Fri, Apr 13, 2007 at 05:33:29PM -0400, Kamaraju S Kusumanchi wrote:
>
>> I want to run software only from Stable (ie Etch) when I am doing
>> non-debian related work. However, when I am doing debian related work
>> (ex :- fi
On Sat, Apr 14, 2007 at 12:15:48AM +0200, Miriam Ruiz wrote:
>These two choices suffer in that you can't get a graphical
> environment within them. So if you build a package for sid
> which used Xorg you couldn't test it.
>
>That's not exactly sure. You'll have a bit overhe
On Fri, Apr 13, 2007 at 11:26:24PM +0100, Steve Kemp wrote:
> On Sat, Apr 14, 2007 at 12:15:48AM +0200, Miriam Ruiz wrote:
>
> >These two choices suffer in that you can't get a graphical
> > environment within them. So if you build a package for sid
> > which used Xorg you could
Le Fri, Apr 13, 2007 at 06:37:41PM -0300, Nelson A. de Oliveira a écrit :
>
> On 4/13/07, Kamaraju S Kusumanchi <[EMAIL PROTECTED]> wrote:
> >Is there any other elegant solution? I have heard about chroot, pbuilder
> >etc., Will they be of any help in this scenario?
>
> Yep. I would go with pbuil
Hi
I think it would be useful, if we can add an index to the maint-guide.
It would be cool if index can be added to other documents such as
debian-reference-en, but I am more concerned for developer's documents. I
can file a wishlist bug, if necessary.
thanks
raju
--
Kamaraju S Kusumanchi
ht
> * Charles Plessy ([EMAIL PROTECTED]) [070413 09:28]:
> > Nevertheless, I tried quilt this week and I like it a
> > lot. Actually, I find it simpler than dpatch because it is not
> > necessary to convert the patches to a special format. I would like to
> > submit a patch to the new maintainer
Hello,
On Fri, 13 Apr 2007, Steve Kemp wrote:
> Sure, I primarily thinking of pbuilder when I wrote that. Sorry!
You can use unionfs wth a (pbuilder) chroot to test most things without
damaging the pristine nature of the build environment.
Secondly you need not run a full-fledged X server unl
Kamaraju S Kusumanchi wrote:
> The easiest idea is to run two machines one with unstable and one with
> stable. But I dont have the luxury of running two machines.
Use vmware/kvm/xen/uml/qemu/whatever... so you can run virtual machines
(very small ones should be ok for doing small developments and
* Charles Plessy ([EMAIL PROTECTED]) [070414 05:19]:
> > * Charles Plessy ([EMAIL PROTECTED]) [070413 09:28]:
> > > Nevertheless, I tried quilt this week and I like it a
> > > lot. Actually, I find it simpler than dpatch because it is not
> > > necessary to convert the patches to a special format
21 matches
Mail list logo
