ris> by virtual packages."
Maybe when it makes sense have things that say provide www-browser
(dealt with through alternatives of course) provide a script
www-browser that does the right thing in this case
#!/bin/sh
exec xemacs -eval "(w3-fetch \"$1\")"
?
Jim
--
@James LewisMoss <[EMAIL PROTECTED]> | Blessed Be!
@http://www.ioa.com/~dres | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
incorporating the fixes within 60 days of the first QA
Chris> Group upload, the package will be marked as orphaned and the
Chris> 'Maintainer' field of the package will be set to "Debian QA
Chris> Group ".''
Remove the "incorporating the fixes" pa
d not uploaded to master until
Wichert> the maintainer has been contacted and the proper NMU
Wichert> procedure has been followed.
Wichert> Can everyone agree with that?
Second from me. One nice thing is to be able to say that we respond
to security problems quickly. This wou
> On Sun, 2 May 1999 07:51:05 -0700, Joseph Carter <[EMAIL PROTECTED]> said:
Joseph> [1 ] On Sun, May 02, 1999 at
Joseph> 11:28:55AM +0100, James Troup wrote:
>> > > We *do* care if, say, Apple comes up with some kind of
>> > > streaming media server and patents the codec.
>> >
>> > This
people are going to propose.
Joey> Anyway, does anyone else agree with Wichert or is he the lone
Joey> objector?
I agree with Wichert. It's already pseudo-policy (everyone pays
attention to it). Why put it into the policy manual now if it will
shortly be changing?
Dres
--
@James
l (with a symlink which should
make everything ok).
2) dpkg's files will stay in /var/lib rather than being moved to
/var/state. This more a survival instinct. Moving these files
could be _very_ bad if not done correctly.
Are there any other divergences that have been discussed? (May
ion IMO.
But things like the emacsen policy where only 20 or so packages depend
upon it at the moment it'd be easier to contact just those 20
developers. And it'd be fine just to do that. Why must debian-policy
become involved when the change is very localized.
Ah well... I'
when things have started
to slow down, but no control over those quickly changing and getting
better packages. No one has argued either that as soon as a sub
policy begins to take shape that it should be taken over by policy.
Only when it has become stable do we add it to the policy package
uld be in the the policy imho, but
Wichert> apparently it is not in there. Anyone in -policy feel like
Wichert> adding this?
/me adds Wichert to the policy doc.
:)
Dres
--
@James LewisMoss <[EMAIL PROTECTED]> | Blessed Be!
@http://www.ioa.com/~dres | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach
ith a transitive dependency? I don't
Branden> see why not; it reduces the number of symlinks that must be
Branden> traversed to get to the final destination.
Why not make C depend on B and A. Then the problem is solved. (with
unallowed transitive dependencies)
Dres
--
@James LewisMos
ist doesn't have a very good configuration setup,
but as long as it works this way and no one fixes it it makes sense to
me to have these as conffiles in /var.
Dres
--
@James LewisMoss <[EMAIL PROTECTED]> | Blessed Be!
@http://www.dimensional.com/~dres | Linux is kewl!
@"Ar
r objections?
I'd prefer something like `The Debian changelog and the copyright file
of a package must be written exclusively in English or provide an English
translation of all content in the same location.'
I don't see a problem with changelogs and copyright files being
written in
ndent on those files.
And heck if you really want a target that is assured to always run
create something like this:
abuild: rmbuild build
rmbuild:
rm -f build
build:
...
Then you can run 'make -f debian/rules abuild' and it will always
rerun build.
Dres
--
k package, and has ignored my requests for more
Ben> information about the bug. It's time to close these bugs, or
Ben> come up with some sort of policy (why, though?) about them.
Twice on xemacs as well. I just closed mine.
Dres
--
@James LewisMoss <[EMAIL PROTECTED]> | Bles
ectories are looked at before LD_LIBRARY_PATH. If this is true
it sounds like a bug in the dynamic linker to me and not libtools. I
don't know that this is the case because I haven't looked at libtool
and how it sets up wrapper scripts.
--
@James LewisMoss <[EMAIL PROTECTED]> | Blessed Be!
@http://www.dimensional.com/~dres | Linux is cool!
@"Argue for your limitations and sure enough, they're yours." Bach
15 matches
Mail list logo
