sergey writes:
> I do not know Debian internal structure well. Is it possible that Debian
> has other place for my suggestion? Some document that give global
> recommendations for cases other than system components interoperability?
Kind of, in the Developer's Reference. There isn't a lot of th
On Sun, 03 Apr 2011 20:17:03 -0700
Russ Allbery wrote:
> Hi sergey,
>
> For the reasons already discussed by others, I don't think that Policy is
> the appropriate place to do this. There's definitely some merit to the
> idea, but I don't think it rises to the level of making it a Policy
> reco
sergey writes:
> What do you think about placing README in each system directory?
> IMHO it make system exploration more interesting for new users and can
> be helpful for expirienced users too.
> Now Debian 6 already contain READMEs in some system directories:
> /etc/init.d/README,
> /etc/grub
Hi Jonathan,
Jonathan wrote:
> It's true that there is no obvious place for feature suggestions with
> no individual taking responsibility (I am hesitant to suggest the
> "general" pseudopackage).
Did you mean category with number 11 from reportbug's list?
$ reportbug
Please enter the name of
(-cc: Steve since he is already subscribed to -policy)
Hi Sergey,
sergey wrote:
> I agree that it is a good place for proposals like mine.
> But making long well-developed draft and "driving" it - this is
> mostly operating system developer's task, not users one.
> I think that Debian should have
Hi Jonathan,
> Policy sets rules that make sure the system works well.
> ...
> Perhaps the following might provide some inspiration:
>
> http://dep.debian.net/deps/dep0/
I agree that it is a good place for proposals like mine.
But making long well-developed draft and "driving" it - this i
Hi Sergey,
sergey wrote:
> Does Debian policy can recommend something (including READMEs)? Or policy can
> only
> force something, no recommendations is possible?
Policy sets rules that make sure the system works well. These can be
hard requirements (generally using the word "must"), which cor
On Fri, 4 Mar 2011 15:33:00 -0600
Jonathan Nieder wrote:
> To throw an idea out, I wonder if making the filesystem hierarchy
> standard (http://www.pathname.com/fhs/) more visible could have the
> same effect? For example, there could be a package providing
> READMEs in system directories contai
Hi Sergey!
sergey wrote:
> What do you think about placing README in each system directory?
I think the idea is interesting but agree with Steve that policy is
not the best way to move it forward. Packages already can put README
files in particularly mysterious directories, and I don't see a
co
On Fri, Mar 04, 2011 at 08:37:45PM +0300, sergey wrote:
> What do you think about placing README in each system directory?
I think it's fine if maintainers of relevant packages want to do this, but
it's not anything that Policy should be enforcing.
> /etc/init.d/README,
I think I was running Deb
Package: debian-policy
Severity: wishlist
Excuse me for my bad English :-)
What do you think about placing README in each system directory?
IMHO it make system exploration more interesting for new users and can be
helpful for
expirienced users too.
Now Debian 6 already contain READMEs in som
11 matches
Mail list logo
