On Wed, Jan 2, 2013 at 3:15 PM, Bernhard R. Link wrote:
> Another question: Have you considered asking for a archive Section for
> those packages? I guess with no special section yet all those packages
> would be section libdevel as they are for static linking only, wouldn't
> they?
http://wiki.d
* Michael Stapelberg [130101 14:45]:
> Furthermore, the package names should be e.g. “golang-codesearch” for
> the library code.google.com/p/codesearch
Please also consider "codesearch-golang". Especially with longer package
names not everything can show the full name so the beginning should be
t
On Tue, Jan 1, 2013 at 6:54 PM, Paul Wise wrote:
> On Wed, Jan 2, 2013 at 12:14 AM, Michael Stapelberg wrote:
>
> > Only when not using the “official” compiler (gc), e.g. gccgo has support
> > for dynamic linking.
>
> Then we should use gccgo until the official compiler supports this.
>
go also
On Wed, Jan 2, 2013 at 12:14 AM, Michael Stapelberg wrote:
> Only when not using the “official” compiler (gc), e.g. gccgo has support
> for dynamic linking.
Then we should use gccgo until the official compiler supports this.
> AFAIK not, but I will add this to the list of questions I want to ask
Hello,
I've just noticed that sphinx2 was orphaned some time ago, and thus
unfortunately dropped from Wheezy. I'd like to reupload it for jessie,
here are the ITPs of the 3 modules:
- Forwarded message from Samuel Thibault -
Package: wnpp
Severity: wishlist
Owner: Samuel Thibault
* Pa
Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg
* Package name: wit
Version : 2.10a
Upstream Author : Dirk Clemens
* URL : http://wit.wiimm.de/
* License : GPL-2+
Programming Lang: C
Description : manipulate Wii and GameCube ISO images and W
Le Tue, Jan 01, 2013 at 10:26:17PM +0800, Thomas Goirand a écrit :
>
> Maybe it's a bit overkill to do a DEP just for that no?
For simple propositions, a DEP is not much more than giving a number to a wiki
page, and keeping track if the proposition is under discussion, accepted or
rejected. The
Package: wnpp
Severity: normal
I request adoption of whohas, a command line tool that allows you to query
several package collections at once.
Regrettably I no longer have the time nor perl-fu to properly look after
this tool (though I will do so where possible for Wheezy). It needs care from
tim
Hi Simon,
Simon McVittie writes:
> Where does gccgo look for Go sources (src)?
> Where does gccgo look for Go "static libraries" (pkg)?
> Where does gccgo look for Go dynamic libraries? (Presumably the same
> places where gcc looks for C dynamic libraries?)
I can’t really answer these questions i
On 01/01/13 16:14, Michael Stapelberg wrote:
> Hi Paul,
>> Support dynamic linking? That would avoid the whole rebuild-the-world
>> thing that statically-linked languages have.
> Only when not using the “official” compiler (gc), e.g. gccgo has support
> for dynamic linking.
Where does gccgo look f
Hi Dmitrijs,
Dmitrijs Ledkovs writes:
> What about multiarch?
I tried to address this on the wiki page, see
http://wiki.debian.org/MichaelStapelberg/GoPackaging#Multi-Arch.2Fcross-compiling
Essentially, I currently believe that multi-arch does not make sense for
go, since we are only dealing wit
On 1 January 2013 15:44, Michael Stapelberg
wrote:
> Hi,
>
> I am co-maintainer of the golang package and spent a few hours on trying
> to figure out how to best create Debian packages for libraries and
> programs which are implemented in Go.
>
> I have documented my thoughts, conclusions and exam
Hi Paul,
> Since golang apparently doesn't support dynamic linking, every package
> built against a golang library will have to include an appropriate
> Built-Using header. You will probably also want a lintian test for
> this to autoreject anything without this header.
Thanks, I was not aware of
On 01/01/2013 04:21 PM, Charles Plessy wrote:
> Hi Thomas and everybody, and « bonne année » !
>
> It seems to me that the main technical arguments advocating predictable or
> sortable release names have been given, so I think that the next step would be
> to make sure that they get to the right ea
On Tue, Jan 1, 2013 at 9:44 PM, Michael Stapelberg wrote:
> Any feedback is appreciated. Please read the wiki page before you
> comment, it contains more rationale than this email. Thanks.
Since golang apparently doesn't support dynamic linking, every package
built against a golang library will h
Hi,
I am co-maintainer of the golang package and spent a few hours on trying
to figure out how to best create Debian packages for libraries and
programs which are implemented in Go.
I have documented my thoughts, conclusions and example packaging on:
http://wiki.debian.org/MichaelStapelberg/GoPac
Hi Thomas and everybody, and « bonne année » !
It seems to me that the main technical arguments advocating predictable or
sortable release names have been given, so I think that the next step would be
to make sure that they get to the right ears at the right time. While this
discussion on -devel
17 matches
Mail list logo
