> Nicolás> That's because root will be just another user, with its set of
> Nicolás> capabilities, and you may like to prevent him from altering
> Nicolás> system files.
>
> Nicolás> As this is a major change, we'd better start now. This will
> Nicolás> also help people who want to implement
>>"Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> But my point is that this is an implementation detail. I can
Joey> envision systems that have no point of return, and can always
Joey> be rolled back (think journaling filesystems).
I guess I do not agree. At this point, the detai
>>"Nicolás" == Nicolás Lichtmaier <[EMAIL PROTECTED]> writes:
Nicolás> That's because root will be just another user, with its set of
Nicolás> capabilities, and you may like to prevent him from altering
Nicolás> system files.
Nicolás> As this is a major change, we'd better start now. This wi
On Wed, 20 Sep 2000, Joey Hess wrote:
> I don't know about the actual code, but that's what the packaging manual
> says and I've never actually seen anyone wrap eg, a depends line (though
> I have a few I'd like to wrap..)
I have, long ago, and I think I've encouraged people to do it..
Can't
It seems that in order to take full advantage of capabilities, files should
not be owned by root. Files should be owned by a non-login user (e.g. bin).
Currently:
-rwxr-xr-x1 root root42300 jul 29 13:26 /bin/ls*
It should be:
-rwxr-xr-x1 bin bin 42300 jul 29
Jason Gunthorpe wrote:
> > We're not really that different. The rfc allows any line to be wrapped,
> > we do not.
>
> Erm, I'd consider any parser which does not allow this to be broken..
I don't know about the actual code, but that's what the packaging manual
says and I've never actually seen an
On Wed, 20 Sep 2000, Joey Hess wrote:
> > Joey> think you should point to that RFC in that section BTW, even
> > Joey> though control file format varies from it in several ways.
> >
> > Color me puzzled. If we are so different from teh RFC, why
> > should we mention it?
>
> We're not rea
Manoj Srivastava wrote:
> Joey> the line. Horizontal whitespace (spaces and tabs) may occur before or
> Joey> after the value and is ignored there; it is conventional to put a
> Joey> single space after the colon.
>
> Joey> Is the space before the colon truely optional? I expect
> Joey>
On 19 Sep 2000, Manoj Srivastava wrote:
> I have put an initial draft of the new package related policy
> manual on http://master.debian.org/%7Esrivasta/new-packaging.txt. I
> have tried to trim tis down to include only stuff I think ought to be
AFIAK this is an error:
All but `Pre
>>"Zed" == Zed Pobre <[EMAIL PROTECTED]> writes:
Zed> I think the confusion lies in the "Horizontal whitespace" line;
Zed> whitespace before the colon is certainly whitespace before the value.
Zed> To make it clearer, perhaps it should read "may occur immediately
Zed> before or after the v
>>"Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> I've seen some typos and typographical errors but I won't
Joey> bother to detail them at this point.
I have now run the manual thriguh ispell, so things should be
better. A new version resides, as usual, at the location:
http://m
Hello,
i am trying to package a program, wnet over the policy, tryed deb-make didn't
found all the info i searched 8means comprehensible examples ot copy of...)
searched for the FAQ and the HOWTO it seamed ot me that they exist
somewhere, would be nice if the links where included in the policy
I've seen some typos and typographical errors but I won't bother to
detail them at this point.
Each paragraph is a series of fields and values; each field consists
of a name, followed by a colon and the value. It ends at the end of
the line. Horizontal whitespace (spaces and tabs)
13 matches
Mail list logo
