Russ Allbery writes:
> I'm hesitant to recommend moving the documentation to /usr/share/doc/foo
> when we've always put it in a directory named after the package in the
> past; I'm afraid long-time Debian users won't be able to find it.
I'd certainly be confused!
Being able to just look in /usr/
Package: wnpp
Severity: wishlist
Owner: Nicholas Bamber
* Package name: libvendorlib-perl
Version : 0.05
Upstream Author : Rafael
* URL : http://search.cpan.org/dist/vendorlib/
* License : perl
Programming Lang: perl
Description : Package to enforce o
Ian Jackson writes:
> Russ Allbery writes ("Re: Directories named after packages"):
>> See http://bugs.debian.org/106073 and the discussion there. Wording
>> proposals very welcome.
> OMG it's from 2001 ...
Yeah, it's almost old enough that I can blame you for the fact that it
wasn't specified
* Roger Leigh schrieb:
> Well, they end up on / to give you /games, /include, /local, /share
> and /src. Because /usr is a symlink to /, these are still accessible
> as /usr/games, /usr/include etc. for full backward compatibility.
If it's just about getting rid of two (lib|bin|sbin) dirs, why
* Bernhard R. Link schrieb:
> They do not only include the library in question, but they include many
> other libraries. As paths supplied by the user are searched in before
> anything in the system path, this changes the order the system paths are
> searched in.
> This can both hide a user supli
* Olaf van der Spek schrieb:
> A transaction to update multiple files in one atomic go?
Yes. The application first starts an transaction, creates/writes/
removes a bunch of files and then sends a commit. The changes
should become visible atomically and the call returns when the
commit() is compl
On Thu, Jan 6, 2011 at 7:33 PM, Enrico Weigelt wrote:
> To come back to the original question, I'd like to know which concrete
> realworld problems should be solved by that. One thing an database-like
> transactional filesystem (w/ MVCC) would be nice is package managers:
> we still have the probl
> Getting people to believe that you can't square a circle[1]
> is very hard,
Just allow an infinite number of steps and it's almost trivial ;-)
> It's like trying teaching a pig to sing.
Well, that works, just sounds a bit like vogon poetry ;-o
> If you give me a specific approach, I can t
Russ Allbery writes ("Re: Directories named after packages"):
> Ian Jackson writes:
>
> > For example, there has been a recent trend for FOO's documentation
> > package FOO-doc to contain /usr/share/doc/FOO-doc/html/index.html (or
> > whatever). I think this is daft. It should be in
> > /usr/sh
Ian Jackson writes:
> For example, there has been a recent trend for FOO's documentation
> package FOO-doc to contain /usr/share/doc/FOO-doc/html/index.html (or
> whatever). I think this is daft. It should be in
> /usr/share/doc/FOO/html/index.html. That way you can find the
> documentation fo
Hi,
On Thu, Jan 06, 2011 at 02:54:38PM +, Ian Jackson wrote:
> Many of the bits of the policy manual, and informal practice, suggest
> naming directories after your package.
>
...
> In general, the principle should be that where to look in the
> filesystem for something should not depend on h
Many of the bits of the policy manual, and informal practice, suggest
naming directories after your package.
I just wanted to make a point that perhaps hasn't been entirely clear:
when we say that you should name the directory after your package, you
should think carefully about what aspect of and
Package: wnpp
Severity: wishlist
Owner: Pierre Chifflier
* Package name: nflog-bindings
Version : 0.1
Upstream Author : Pierre Chifflier
* URL :
https://www.wzdftpd.net/redmine/projects/nflog-bindings/wiki/
* License : GPLv3
Programming Lang: C, Python, Per
Hi,
so googleearth-package was removed from squeeze, because of a RC bug, which
was fixed on mentors.d.n for 4 days already when it was removed. Sadly the
maintainer didnt ask for sponsorship on the mentors-list, so his uploaded was
not noticed immediatly.
Then, 605959 asking for its removal w
On Thu, Jan 6, 2011 at 12:39 PM, Olaf van der Spek wrote:
> On Thu, Jan 6, 2011 at 5:01 AM, Ted Ts'o wrote:
>> On Thu, Jan 06, 2011 at 12:57:07AM +, Ian Jackson wrote:
>>> Ted Ts'o writes ("Re: Safe File Update (atomic)"):
>>> > Then I invite you to implement it, and start discovering all of
On Thu, Jan 6, 2011 at 5:01 AM, Ted Ts'o wrote:
> On Thu, Jan 06, 2011 at 12:57:07AM +, Ian Jackson wrote:
>> Ted Ts'o writes ("Re: Safe File Update (atomic)"):
>> > Then I invite you to implement it, and start discovering all of the
>> > corner cases for yourself. :-) As I predicted, you're
* Ted Ts'o [110105 19:26]:
> So one of the questions is how much should be penalizing programs that
> are doing things right (i.e., using fsync), versus programs which are
> doing things wrong (i.e., using rename and trusting to luck).
Please do not call it "wrong". All those programs doing is no
On Thu, Jan 6, 2011 at 1:54 AM, Ted Ts'o wrote:
>> I was thinking, doesn't ext have this kind of dependency tracking already?
>> It has to write the inode after writing the data, otherwise the inode
>> might point to garbage.
>
> No, it doesn't. We use journaling, and forced data writeouts, to
>
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: scannedonly
Version: 0.21
Upstream Author: Olivier sessink o...@users.sourceforge.net]
URL: http://olivier.sessink.nl/scannedonly
Lic
19 matches
Mail list logo
