t realise you can second your own proposal, but I'm happy to
second my proposal in that case, so seconded too.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of &quo
]] Aurelien Jarno
> On Thu, May 08, 2014 at 09:08:58AM +0200, Tollef Fog Heen wrote:
> > ]] Aurelien Jarno
> >
> > > How can we progress on this bug? We now have bugs #720777, #720778 and
> > > #720780 which ask for /usr/lib to be created if /lib exists.
esumably blocked on more
seconds.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx90927p@xoog.err.no
of fallout.
I'm not at all convinced invoke-rc.d is the right interface for this,
partially due to you easily ending up with cycles such as seen in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635777 where postfix
depends on network being up, but the network isn't considered up until
ation. I wonder if something like the emacsen-hooks mechanism
would make sense or if we should consider the rcN.d links to be
authoritative and it being up to the init system to make sure it
respects the state set by the symlinks.
--
Tollef Fog Heen
UNIX is user friendly, it's just pi
ow to
handle all of sysvinit, upstart and systemd or if we want each init
system to ship their own. From the patch, it looks like each init
system should ship their own, but that it still must keep compatibility
with all other implementations.
Also, I'm a bit annoyed about you grabbing /etc/init,
st for this too.
Regards,
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.
Package: debian-policy
]] Steve Langasek
| On Fri, Feb 04, 2011 at 07:02:33PM +0100, Tollef Fog Heen wrote:
| > ]] Yaroslav Halchenko
|
| > | please do not slap me too hard (only so that I feel your warm carrying
| > | touch):
|
| > | is there a rationale for: on amd64 Debian sy
e added to the insserv configuration file. We should
either require init implementations to allow providing the standardised
facility names or we should put that information somewhere in a a
neutral location and format so all init implementations can make use of
it.
Best regards,
--
Tollef Fog Hee
]] Steve Langasek
| We don't really want extra -L options passed to the build for every
| library that's installed to the multiarch lib dir. Does pkgconfig
| filter these out?
Not yet.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
r/bin/make -f»
too. There's no reason to mandate one particular style of hashbangs.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe&q
the
other changing.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
for), you need to use
pkg-config. pkg-config allows you to, say, move all the headers from
each package into its own namespace, like how GTK+ and Glib does it
and you can then rename that later if you so wish, without causing
FTBFS-es.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky abo
* (Marco d'Itri)
| Actually I am almost sure that there are some situations in which PIC
| static libraries are useful, but I cannot provide examples right now.
If you need to integrate them into another .so/build reduced
libraries, like what mklibs does for d-i.
--
Tollef Fog
* Thomas Hood
| The following (bash-only) function seems to have the desired properties.
If it's bash-only, wouldn't using bash + command -v be easier? :)
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's
do what command -v does. (Actually, it does a bit more, as it
can do stuff like:
: [EMAIL PROTECTED] ~ > findcommand foo bar baz xterm
/usr/X11R6/bin/xterm
(which is _very_ useful for me when I'm doing something approaching
per-user cross
* Colin Walters
| On Sat, 2003-01-04 at 19:22, Tollef Fog Heen wrote:
|
| > And any hard coded scripts using -d norsk (or -d bokmal) for getting
| > Norwegian ispell output.
|
| Hm, but if the filename is already UTF-8, what is the problem?
It isn't in stable, which means that I w
* Colin Walters
| On Sat, 2003-01-04 at 13:15, Tollef Fog Heen wrote:
| > * Colin Walters
| >
| > | Note that in my proposal UTF-8 filenames are only mandatory (a "must")
| > | for files *included directly* in Debian packages or created by
| > | maintainer scripts. Si
ext upload of mailman.
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
`. `'
`-
e a thing.
You are wrong in this regard. inorwegian includes a file called
bokmål (which, ISTR, has symlinks for both ISO8859-1 and UTF8)
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
`. `'
`-
fining alternative changelog formats
|
|
- --
Tollef Fog Heen,''`.
UNIX is user frien
cause a lot of
packages (you know how many?) to be instantly buggy. If you change
the «must» to «should», I'll second the proposal.
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
`. `'
`-
as a static library and
| > usage of static libraries should be deprecated except for a few
| > specific cases.
|
| I'd be curious to know of an example of a "modern library" which doesn't
| work well when compiled statically.
libc6 fuc
d cdebconf better substitutes for each other.
Seconded.
- --
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky
* Manoj Srivastava
| Is that indeed the case? If not, we have to wait before we can
| include this bit in policy.
No, it is not the case. Yet.
--
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about
uldn't be done.
|
| Did all of you manage to miss sed's y command?
|
| #!/bin/sh
| sed "y/$1/$2/"
I'm not saying I'm a sed guru, but
: [EMAIL PROTECTED] ~ > echo ABCD | tr A-Z a-z
abcd
: [EMAIL PROTECTED] ~ > echo ABCD | sed 'y/A-Z/a-z/'
aBCD
doe
root root 395048 apr 27 18:34 /bin/zsh-4.0.4*
$ ls -l /etc/alternatives/csh
lrwxrwxrwx1 root root 12 mai 2 15:25 /etc/alternatives/csh
-> /bin/bsd-csh*
so, csh and zsh are both in /bin
--
Tollef Fog Heen,&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 89867 normal
retitle 89867 [AMENDMENT 18/02/2002] Where to place web-accessible images
thanks
Also, please note that the diff is reversed; it should be obvious, but
apparently I did something strange.
- --
Tollef Fog Heen
Unix _IS_ user
/usr/share/images/package
- and can be referred to as
-
- http://localhost/images/<package>/<filename>;
-
Web Document Root
(btw, should proposals be GPG signed? policy-prosess doesn't say
anythin
es create sub-directories, so that
Mailman will have /usr/share/images/mailman/logo.jpg which will be
referred to as http://server/images/mailman/logo.jpg .
--
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about who its friends are.
30 matches
Mail list logo
