Branden Robinson <[EMAIL PROTECTED]> writes:
> On Sat, Nov 09, 2002 at 04:25:00PM +0100, Sebastian Rittau wrote:
> > Package: debian-policy
> > Version: 3.5.7.0
> > Severity: wishlist
> >
> > I suggest the following alteration to the policy:
>
> I object strenuously to this proposal.
Me too.
Joey Hess <[EMAIL PROTECTED]> writes:
> Adrian Bunk wrote:
> > could someone else please read the discussion in #96458 answer Philippe?
> > I'm tired of this frustrating discussion with someone who tried to make
> > xv a native Debain package.
>
> Well Phil is clearly ignoring the intent of polic
On Sat, 21 Mar 1998 08:20:37 MST Galen Hazelwood ([EMAIL PROTECTED])
wrote:
> The current situation regarding gcc is rather complex.
>
> I had fully intended to make egcc the standard gcc for debian.
> Unfortunately, a lot of people complained. Some of their complaints
> were very serious: aft
On 30 Nov 1997 18:28:23 EST Ben Pfaff ([EMAIL PROTECTED]) wrote:
> Philippe Troin <[EMAIL PROTECTED]> writes:
> > Two packages instead of one. We have 1400+ packages in main (around 2000
> > including non-free and contrib), and I think we should apply care when
>
On 30 Nov 1997 13:06:00 CST Rob Browning ([EMAIL PROTECTED]) wrote:
> Ben Pfaff <[EMAIL PROTECTED]> writes:
>
> > Rob Browning <[EMAIL PROTECTED]> writes:
> > > 1) Create two packages: foo and foo-tk
> >
> > I can't see any real downsides to this. If `foo' suggests `foo-tk'
> > (and `foo-tk'
On Thu, 27 Nov 1997 20:52:35 CST David Engel ([EMAIL PROTECTED]) wrote:
> On Thu, Nov 27, 1997 at 03:07:02PM +0800, Philippe Troin wrote:
> >
> > libfoo-altdev depends on libfoog-dev
>
> I disagreed with this last one. The reason is that it prevents the
> user
Having some arguments with someone about dependencies of libraries,
I've posted here to have this sorted out.
Assume you have:
libfoo libc5 compatibility library
libfoo-altdevlibc5 compatibility development package
libfoog libc6 library
libf
7 matches
Mail list logo
