> > I was hoping to ship at most one package per version. There's simply
> > no way that ftpmasters are going to allow shipping a single manpage in
> > each package. My original thought was gcc-manpages, but if you'd
> > prefer a single package per version, I can do that, too.
>
> fine too. but f
On 01/09/2012 08:22 PM, brian m. carlson wrote:
> On Mon, Jan 09, 2012 at 07:29:08PM +0100, Matthias Klose wrote:
>> On 01/07/2012 08:51 PM, brian m. carlson wrote:
>>> Do you have a preference on the name of the package?
>>
>> what about {cpp,gcc,g++,gfortran}-4.x-man?
>
> I was hoping to ship at
On Mon, Jan 09, 2012 at 07:29:08PM +0100, Matthias Klose wrote:
> On 01/07/2012 08:51 PM, brian m. carlson wrote:
> > Do you have a preference on the name of the package?
>
> what about {cpp,gcc,g++,gfortran}-4.x-man?
I was hoping to ship at most one package per version. There's simply no
way th
On 01/07/2012 08:51 PM, brian m. carlson wrote:
> Do you have a preference on the name of the package?
what about {cpp,gcc,g++,gfortran}-4.x-man?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sat, Jan 07, 2012 at 07:28:37PM +0100, Matthias Klose wrote:
> we have the original man pages in non-free (at least we had these packaged for
> earlier versions [1]; feel free to package these, I assume Nikita would
> welcome
> the help). These are far better than anything written from scratch
> On 01/07/2012 05:36 PM, brian m. carlson wrote:
> > On Sat, Jan 07, 2012 at 07:53:25AM +0100, Matthias Klose wrote:
> >> won't fix in the gcc-4.6 package; clearly these "skeletal" pages are
> >> not part of the upstream sources. please package those as a separate
> >> package if you intend to mai
On 01/07/2012 05:36 PM, brian m. carlson wrote:
> On Sat, Jan 07, 2012 at 07:53:25AM +0100, Matthias Klose wrote:
>> won't fix in the gcc-4.6 package; clearly these "skeletal" pages are
>> not part of the upstream sources. please package those as a separate
>> package if you intend to maintain thes
On Sat, Jan 07, 2012 at 07:53:25AM +0100, Matthias Klose wrote:
> won't fix in the gcc-4.6 package; clearly these "skeletal" pages are
> not part of the upstream sources. please package those as a separate
> package if you intend to maintain these on a regular basis.
Lots of Debian packages includ
tags 654931 + wontfix
thanks
On 01/06/2012 11:12 PM, brian m. carlson wrote:
> Package: gcc-4.6
> Version: 4.6.2-11
> Severity: wishlist
> Tags: patch
>
> gcc-4.6 and company are missing manpages. I am aware that this is a
> result of the upstream manpages being non-free.
> Since policy require
Package: gcc-4.6
Version: 4.6.2-11
Severity: wishlist
Tags: patch
gcc-4.6 and company are missing manpages. I am aware that this is a
result of the upstream manpages being non-free. Since policy requires a
manpage for each binary, I am including a skeletal manpage that covers
some of the most co
10 matches
Mail list logo