Mark Brown <[EMAIL PROTECTED]> wrote:
> when building. It thinks it needs root to set the ownership of files to
> root (among other things), but in actual fact dpkg will do the right thing
Ahh, that actually makes sense.
> What package building does is very much like installing using a tool
> like stow - you build the package, and then install it into its own
> directory tree. This usually uses whatever procedures the package uses,
> so a lot of times install is involved. After this the appropriate wands
> are waved to pull everything into .debs and source package.
I've heard of stow not too familiar with how it works though. Thanks
for the info.
> information isn't pushed at users.
This is a real pity. I've known at least a couple of Debian users
who've struggled to build .debs from source packages or who've wanted
to roll their own .deb so that the system could keep track of the
files ultimately they give up in disgust... There is certainly no FAQ
I could find dealing with this.
>> > Personally I always found dpkg easier than RPM for building packages,
>> > but perhaps it's just me.
>
>> IIRC all it took to build SRPMS is one single rpm command.
>
> I know, but I never felt like I was in control. It also seemed very
I guess if you wanted that control then you'd have to edit the SRPM
(SPEC file, I believe).
> attached to using /usr/src and leaving files around there.
Ugh, typical Red Hat.
-N.
--
"These download files are in Microsoft Word 6.0 format. After unzipping,
these files can be viewed in any text editor, including all versions of
Microsoft Word, WordPad, and Microsoft Word Viewer." [Microsoft website]
< http://www.cs.mcgill.ca/~navindra/editors/ >
