OK, Paul has talked about embedded copies which I agree with (leaving
aside the whole jquery thing) in general. Use the already packaged
libraries for that, your life will be better for it!
Turning to copyright files, the preferred format is the old DEP-5
format, found at [1]
The files stanzas, t
On Sat, Jun 13, 2015 at 10:30 AM, wrote:
> https://code.google.com/p/uftt/source/browse/trunk/src/linux/libnetlink.c?r=1041
It looks like this code has several copies already in Debian. The
proper upstream for this file seems to be iproute2 but that only
builds a static library that isn't insta
On Sat, Jun 13, 2015 at 10:30 AM, wrote:
> Hello, this is my first time publishing a program i have made
...
> Also at the debian/copyright file. The lines should be something like that?
> Code was taken from here:
> https://github.com/seanmiddleditch/libtelnet
> https://code.google.com/p/uftt/s
On Sat, Jun 13, 2015 at 6:36 AM, Azat Khuzhin wrote:
> * QA upload
> * New maintainer. (Closes: #695127).
Uploads can either be QA uploads (one-shot only) or uploads by the new
maintainer but never both. Please pick one and remove the other one.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Hello, this is my first time publishing a program i have made, i would like
you to explain me some things about copyrights, i was reading about
copyright for packaging a program i made at Debian and i could not
understand/fill some parts. From all the source code files, i have used 4
that are not
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "blktool"
Package name: blktool
Version : 4-7
Upstream Author : Jeff Garzik
URL : http://sourceforge.net/projects/gkernel/files/blktool/
License : GPL v2
lumin writes:
> Is there any problem with "-rpath" that needs a fix ?
https://wiki.debian.org/RpathIssue
--
Feri.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.or
On Fri, Jun 12, 2015 at 03:16:00PM +, lumin wrote:
> > > NOTE: libsharedlib1 has no SONAME
> > If it has no SONAME then this won't work. Shared libraries should have
> > SONAMEs (also, where that 1 does come from then?).
> Well, upstream doesn't set SONAME, and ..
All public shared li
Hi Andrey Rahmatullin,
> > NOTE: libsharedlib1 has no SONAME
> If it has no SONAME then this won't work. Shared libraries should have
> SONAMEs (also, where that 1 does come from then?).
Well, upstream doesn't set SONAME, and ..
if I just put .so libs together with executables into into
-- Forwarded message --
From: Joël Krähemann
Date: Thu, Jun 11, 2015 at 4:54 PM
Subject: Re: Introducing myself - Joël Krähemann
To: "IOhannes m zmölnig (Debian/GNU)"
Hi, sorry for the circumstances here is it:
jkraehemann
I've already done my first package for sure it needs t
On Fri, Jun 12, 2015 at 08:11:14AM +, lumin wrote:
> And I'd like to package it as following:
>
> package: hello
> depends: libsharedlib1
> package: libsharedlib1
> NOTE: libsharedlib1 has no SONAME
If it has no SONAME then this won't work. Shared libraries
Hi mentors,
I've been struggling with this shared library linking issue for
a while.
I scanned maint-guide, dev-ref (detail not enough),
debmake-doc (osamu's new version of maint-guide),
and a library packaging guide [1] that debmake-doc recommended.
Then I still have no idea how to handle the pro
12 matches
Mail list logo
