On Mon, 1 Dec 2014 10:27:52 Paul Wise wrote:
Personally I prefer to separate packaging from upstream development
because they are two different things. When I use a VCS for packaging
it contains only the debian/ directory.
This is how I like to handle Debian packaging in git as well.
--
On Sunday 30 November 2014 20:32:26 T o n g wrote:
On Sun, 30 Nov 2014 18:12:06 +0100, Santiago Vila wrote:
In the past, having a `debian/` directory upstream was a pain because
we didn't have a proper way to remove a file if needed. Nowadays, it
is perfectly fine if you use a 3.0
Hi,
I'm currently hosting my self-maintained Debian packages on GitHub. Here
is my dilemma:
- It is commonly recommended not to put the `debian` folder within the
source tree so as to make it easier for other distros.
- So I did. I did not put my `debian` folder within the source tree on
❦ 30 novembre 2014 14:06 GMT, T o n g mlist4sunt...@yahoo.com :
I'm currently hosting my self-maintained Debian packages on GitHub. Here
is my dilemma:
- It is commonly recommended not to put the `debian` folder within the
source tree so as to make it easier for other distros.
In the
Hello Forum,
On 30/11/14 16:30, Vincent Bernat wrote:
❦ 30 novembre 2014 14:06 GMT, T o n g mlist4sunt...@yahoo.com :
I'm currently hosting my self-maintained Debian packages on GitHub. Here
is my dilemma:
- It is commonly recommended not to put the `debian` folder within the
source
On Sun, Nov 30, 2014 at 05:31:00PM +0100, Jerome BENOIT wrote:
On 30/11/14 16:30, Vincent Bernat wrote:
In the past, having a `debian/` directory upstream was a pain because we
didn't have a proper way to remove a file if needed. Nowadays, it is
perfectly fine if you use a 3.0 format.
On Sun, 30 Nov 2014 18:12:06 +0100, Santiago Vila wrote:
In the past, having a `debian/` directory upstream was a pain because
we didn't have a proper way to remove a file if needed. Nowadays, it
is perfectly fine if you use a 3.0 format.
Fine in which way ?
It's fine because, for a
On Mon, Dec 1, 2014 at 4:32 AM, T o n g wrote:
Ok, good to know, but that's more targeting towards package building, not
source code developing and maintaining. Does it imply that I should put
the `debian` folder within my source tree now? Because as mentioned
before, the last thing I want to
T o n g mlist4sunt...@yahoo.com writes:
Ok, good to know, but that's more targeting towards package building,
not source code developing and maintaining. Does it imply that I should
put the `debian` folder within my source tree now? Because as mentioned
before, the last thing I want to do is
9 matches
Mail list logo
