On Mon, 5 Mar 2007 12:26:29 +0800
"Monty Taylor" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is there a sensible way to the list of -I options passed to
> dpkg-source?
>
> My tree has SCCS dirs and I would like to exclude them, but I'd like
> to do it in the most sensible way I can...
Any kind of so
Hi all,
Is there a sensible way to the list of -I options passed to dpkg-source?
My tree has SCCS dirs and I would like to exclude them, but I'd like
to do it in the most sensible way I can...
Thanks!
Monty
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble
On Sun, Mar 04, 2007 at 11:51:47AM +0100, Bart Martens wrote:
> On Sun, 2007-03-04 at 12:15 +0200, Damyan Ivanov wrote:
> >
> > Shouldn't the source package name reflect that it has been re-packaged?
> > Something like "legends-0.4.1.42.ds.1" ?
>
> It should be documented in debian/README.Debian-
On Mon, 2007-01-29 at 16:08 +0800, Thomas Goirand wrote:
> Hi!
>
> I have few questions that would help me to solve things in my package. I
> have package1 and package2 being same but with different dependencies,
> so the user can choose between them.
>
> First, if my package produces many binary
Dear mentors,
I have update the package chessdb to the new version released by the
upstreamer,
* Package name: chessdb
Version : 3.6.15-1
Upstream Author : David Kirkby
* URL : http://chessdb.sourceforge.net
* License : GPL
Section : games
ChessDB
On Sun, 2007-03-04 at 12:15 +0200, Damyan Ivanov wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> - -=| Bart Martens, 4.03.2007 01:11 |=-
> > Related to what Roberto wrote above about the shared libraries, here is
> > how I would create the .orig.tar.gz :
> >
> > sh legends_linux-0.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -=| Bart Martens, 4.03.2007 01:11 |=-
> Related to what Roberto wrote above about the shared libraries, here is
> how I would create the .orig.tar.gz :
>
> sh legends_linux-0.4.1.42.run --noexec --keep --nox11 \
> --target legends-0.4.1.42/legends
Russ Allbery <[EMAIL PROTECTED]> wrote:
> I still think that debian/copyright is a more natural location for this
> information. debian/copyright is where we're required to specify the
> source of the upstream tarball. Any customizations to the upstream
> tarball seem to me to be part and parcel
Florent Rougon <[EMAIL PROTECTED]> writes:
> Daniel Leidert <[EMAIL PROTECTED]> wrote:
>>> Definitely README.Debian; probably a good idea in "copyright", where you
>>> mention the download location.
> The Developers Reference gives several useful hints for this situation
> and suggests[1] to use
Hi,
Daniel Leidert <[EMAIL PROTECTED]> wrote:
>> Definitely README.Debian; probably a good idea in "copyright", where you
>> mention the download location.
The Developers Reference gives several useful hints for this situation
and suggests[1] to use a more specific file: README.Debian-source.
10 matches
Mail list logo