On Thu, Jul 19, 2001 at 06:57:11PM +, [EMAIL PROTECTED] wrote:
> somebody other than root, don't use fakeroot to build the package,
> because it forces everything to look like it's owned by root.
Wrong. It remembers permissions and ownership of files within the
same session. However, no chan
On Thu, Jul 19, 2001 at 06:57:11PM +, [EMAIL PROTECTED] wrote:
> somebody other than root, don't use fakeroot to build the package,
> because it forces everything to look like it's owned by root.
Wrong. It remembers permissions and ownership of files within the
same session. However, no cha
On Fri, Jul 20, 2001 at 11:24:31AM -0400, Richard A Nelson wrote:
> > > install: install-stamp
> > > install-stamp: build-stamp
> > > install stuff
> > > chown someuser stuff
> > >
> > > binary-arch: install-stamp
> > > build package
> > >
> > BTW install-stamp is evil
Nicolas SABOURET wrote:
> I may be wrong, but as far as I understood, dh_fixperms is responsible
> for changing the owner of the files :
>
> $man dh_fixperms
> [...]It makes all files be owned by
>root, and it removes group and other write permission from
>
On Fri, Jul 20, 2001 at 10:21:37AM +0200, Robert Bihlmeyer wrote:
> It should be noted that this requirement is broken when your rules
> have something like:
>
> install: install-stamp
> install-stamp: build-stamp
> install stuff
> chown someuser stuff
>
> binary-arch: insta
On Fri, Jul 20, 2001 at 11:24:31AM -0400, Richard A Nelson wrote:
> > > install: install-stamp
> > > install-stamp: build-stamp
> > > install stuff
> > > chown someuser stuff
> > >
> > > binary-arch: install-stamp
> > > build package
> > >
> > BTW install-stamp is evi
Nicolas SABOURET wrote:
> I may be wrong, but as far as I understood, dh_fixperms is responsible
> for changing the owner of the files :
>
> $man dh_fixperms
> [...]It makes all files be owned by
>root, and it removes group and other write permission from
>
On Fri, Jul 20, 2001 at 10:21:37AM +0200, Robert Bihlmeyer wrote:
> It should be noted that this requirement is broken when your rules
> have something like:
>
> install: install-stamp
> install-stamp: build-stamp
> install stuff
> chown someuser stuff
>
> binary-arch: inst
[EMAIL PROTECTED] writes:
> > >because it forces everything to look like it's owned by root. Use
> > >sudo.
> >
> > That's not true:
>
> You're right, as long as you haven't exited fakeroot and started it up
> again in the meantime; I didn't realize that.
It should be noted that this require
[EMAIL PROTECTED] writes:
> > >because it forces everything to look like it's owned by root. Use
> > >sudo.
> >
> > That's not true:
>
> You're right, as long as you haven't exited fakeroot and started it up
> again in the meantime; I didn't realize that.
It should be noted that this requir
I may be wrong, but as far as I understood, dh_fixperms is responsible
for changing the owner of the files :
$man dh_fixperms
[...]It makes all files be owned by
root, and it removes group and other write permission from
all files. [...]
Nicolas.
S
I may be wrong, but as far as I understood, dh_fixperms is responsible
for changing the owner of the files :
$man dh_fixperms
[...]It makes all files be owned by
root, and it removes group and other write permission from
all files. [...]
Nicolas.
> >because it forces everything to look like it's owned by root. Use
> >sudo.
>
> That's not true:
You're right, as long as you haven't exited fakeroot and started it up
again in the meantime; I didn't realize that.
--
thanks,
[EMAIL PROTECTED] wrote:
>For situations where you need a file in debian/tmp to be owned by
>somebody other than root, don't use fakeroot to build the package,
>because it forces everything to look like it's owned by root. Use
>sudo.
That's not true:
[EMAIL PROTECTED] ~]$ fakeroot
[EMAIL PRO
[EMAIL PROTECTED] wrote:
> The short answer is to have them owned by the correct person in the
> debian/tmp (or, which newer debhelper versions, debian/)
> directory.
Right.
> For situations where you need a file in debian/tmp to be owned by
> somebody other than root, don't use fakeroot to bu
> >because it forces everything to look like it's owned by root. Use
> >sudo.
>
> That's not true:
You're right, as long as you haven't exited fakeroot and started it up
again in the meantime; I didn't realize that.
--
thanks,
Steve McWilliams <[EMAIL PROTECTED]> wrote:
>I have read through the debian packaging documentation and am playing
>around with it currently, however I have not yet figured out how to
>control the ownership of files installed from a binary debian package.
>I realize that normally installed package
The short answer is to have them owned by the correct person in the
debian/tmp (or, which newer debhelper versions, debian/)
directory.
For situations where you need a file in debian/tmp to be owned by
somebody other than root, don't use fakeroot to build the package,
because it forces everything
[EMAIL PROTECTED] wrote:
>For situations where you need a file in debian/tmp to be owned by
>somebody other than root, don't use fakeroot to build the package,
>because it forces everything to look like it's owned by root. Use
>sudo.
That's not true:
[cjw44@riva ~]$ fakeroot
[root@riva ~]#
[EMAIL PROTECTED] wrote:
> The short answer is to have them owned by the correct person in the
> debian/tmp (or, which newer debhelper versions, debian/)
> directory.
Right.
> For situations where you need a file in debian/tmp to be owned by
> somebody other than root, don't use fakeroot to b
Hello,
I have read through the debian packaging documentation and am playing
around with it currently, however I have not yet figured out how to
control the ownership of files installed from a binary debian package.
I realize that normally installed package files should be owned by root,
however I
Steve McWilliams <[EMAIL PROTECTED]> wrote:
>I have read through the debian packaging documentation and am playing
>around with it currently, however I have not yet figured out how to
>control the ownership of files installed from a binary debian package.
>I realize that normally installed package
The short answer is to have them owned by the correct person in the
debian/tmp (or, which newer debhelper versions, debian/)
directory.
For situations where you need a file in debian/tmp to be owned by
somebody other than root, don't use fakeroot to build the package,
because it forces everything
Hello,
I have read through the debian packaging documentation and am playing
around with it currently, however I have not yet figured out how to
control the ownership of files installed from a binary debian package.
I realize that normally installed package files should be owned by root,
however
24 matches
Mail list logo
