How to handle software which needs huge modification when packaging for Debian

To: debian-mentors@lists.debian.org
Subject: How to handle software which needs huge modification when packaging for Debian
From: Björn Esser <bjoern.esser@googlemail.com>
Date: Mon, 16 Jan 2012 21:47:51 +0100
Message-id: <[🔎] 4F148CF7.4040808@googlemail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi there!

How shall software be handled, when it needs

    - huge modifactions
    - scripts to be replaced by 'debianized' ones
    - to be extended by custom scripts or progs

when packaging it for debian?

Shall the custom / replaced stuff be placed inside
debian/source/include-binaries?

Or should it be forked from upstream and seperately developed as
debian-native?

BR,

Björn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk8UjPIACgkQ3u1SIc8s7PUFXAD/dlexMpz32mX7x//rv7/G4r7P
kCoD3EAvpZDdT8yqYGEBAJMNGjPHALsBlDVVlcvCwKSIp8QJ0nZodMtYPYLIRkVk
=YXpU
-----END PGP SIGNATURE-----

Reply to:

Follow-Ups:
- Re: How to handle software which needs huge modification when packaging for Debian
  - From: Paul Wise <pabs@debian.org>
- Re: How to handle software which needs huge modification when packaging for Debian
  - From: Alexey Eromenko <al4321@gmail.com>

Prev by Date: Re: RFS: libpam-abl , bug fix , package is already in Debian
Next by Date: Re: How to handle software which needs huge modification when packaging for Debian
Previous by thread: Re: RFS: libpam-abl , bug fix , package is already in Debian
Next by thread: Re: How to handle software which needs huge modification when packaging for Debian
Index(es):
- Date
- Thread