> > It occurred to me that I could try to work around
> this by using a
> > build directory that is completely outside of the
> source code tree.
Hello,
My own experience is something like this; by the
way, I am also a newbie to packaging, so this is just
what works for me, not necessarily wha
Hi Paul
I have also found the migration from RPM packaging to Debian packaging
to be a hard one (I'm *not* a mentor, BTW). Some of my observations include:
1. Whereas RPM provides one key tool, 'rpmbuild', Debian packaging
seems to provide dozens of different tools, not all of which are
On Fri, 30 May 2008 22:25:44 +0100, Neil Williams <[EMAIL PROTECTED]> said:
> On Fri, 2008-05-30 at 15:07 -0500, Paul Johnson wrote:
>> Keep in mind that my background is in RPM building, where the
>> emphasis is on distributing "pristine" source code. I was initially
>> shocked/dismayed by the
On Fri, 30 May 2008 15:07:57 -0500, Paul Johnson <[EMAIL PROTECTED]> said:
> Keep in mind that my background is in RPM building, where the emphasis
> is on distributing "pristine" source code. I was initially
> shocked/dismayed by the Debian approach because the source code gets
> untarred and f
Paul Johnson wrote:
> While testing
> this out, I realize I've made some mistakes while attempting to revise
> the Makefile to match the packaging requirements. It appears to me
> that I have to 1) move the debian directory to a safe place, 2) erase
> the code tree, 3) untar a fresh copy, 4) copy
* Paul Johnson <[EMAIL PROTECTED]> [080530 22:08]:
> Keep in mind that my background is in RPM building, where the emphasis
> is on distributing "pristine" source code. I was initially
> shocked/dismayed by the Debian approach because the source code gets
> untarred and fiddled with by the package
Hello,
On Fri, 30 May 2008, Paul Johnson wrote:
> I've been asking around for help on building debian packages.
> changes, and all of those fiddles were getting wrapped up into the one
> big diff file, making it impossible to figure out who did what.
One possible reason to do this is that the pe
Le Fri, May 30, 2008 at 03:07:57PM -0500, Paul Johnson a écrit :
>
> I keep wondering, "If the goal is to re-distribute 'pristine' source
> code and patches, why doesn't Debian discourage users from untarring
> the sourced code?"Why can't you make it so the debian directory is
> not inside the
On Fri, 2008-05-30 at 15:07 -0500, Paul Johnson wrote:
> Keep in mind that my background is in RPM building, where the emphasis
> is on distributing "pristine" source code. I was initially
> shocked/dismayed by the Debian approach because the source code gets
> untarred and fiddled with by the pac
OoO En cette soirée bien amorcée du vendredi 30 mai 2008, vers 22:07,
"Paul Johnson" <[EMAIL PROTECTED]> disait:
> I wonder how you do your day-to-day work on building debs? I have
> followed the dh_make approach of opening the source, and dh_make gives
> me template files in "debian" for co
Hi I'm new here.
I've been asking around for help on building debian packages. I've
been building RPMS for about 1 decade, but never tried to build a
Debian package. As preparation, I've read through the New
Maintainer's Guide and miscellaneous other web pages. I came in
through the Ubuntu do
11 matches
Mail list logo
