On Thu, Mar 17, 2011 at 3:35 AM, Henrique de Moraes Holschuh
wrote:
> Well, I have been doing this, for a LONG time, to preserve my sanity when
> working as upstream or in a native auto-tooled package:
>
> 1. No spawn from autotooling allowed in the VCS. EVER. .gitignore it
> away at once. A
Package: wnpp
Severity: wishlist
Owner: Andrew Ross
* Package name: flamingo
Version : 5.0
Upstream Author : Kirill Grouchnikov
* URL : https://flamingo.dev.java.net/
* License : BSD
Programming Lang: Java
Description : A Swing ribbon container for Jav
On Wed, Mar 16, 2011 at 02:01:37PM +, Ian Jackson wrote:
> Well surely the question is: why are the files moved to a different
> directory ? Why is the package renamed, even ? Do we need to be able
> to co-install the old and new ISC DHCP clients ?!
The original dhcp-client was version 2. d
On Sun, Mar 13, 2011 at 03:20:21PM +0100, David Kalnischkies wrote:
> On Sun, Mar 13, 2011 at 13:32, Svante Signell
> wrote:
> > when apt-updating from ftp.se.debian.org i get the following Hash Sum
> > mismatch failures:
> > (it does not happen when using ftp.us.debian.org in sources.list)
>
>
On Tue, Mar 15, 2011 at 09:12:54PM +0100, Florian Lohoff wrote:
> On Tue, Mar 15, 2011 at 04:05:59PM +0100, Bernd Zeimetz wrote:
> > On 03/13/2011 05:53 PM, Hideki Yamane wrote:
> > > On Sun, 13 Mar 2011 15:20:21 +0100
> > > David Kalnischkies wrote:
> > >> Unfortunately many mirrors doesn't use t
Package: wnpp
Severity: wishlist
Owner: Mohammed Sameer
* Package name: libreoffice-autocorrect-ar
Version : 0.1
Upstream Author : Taha Zerrouki
* URL : http://ghalatawi.sourceforge.net/
* License : GPL
Description : Arabic autocorrect files for LibreOff
On Wed, 16 Mar 2011, Neil Williams wrote:
> On Tue, 15 Mar 2011 23:35:59 +
> Ben Hutchings wrote:
> > On Tue, Mar 15, 2011 at 10:55:54PM +, Neil Williams wrote:
> > > Other tools, like svn-buildpackage, don't have this problem, via the
> > > mergeWithUpstream support and/or a ../tarballs/
On Tue, 15 Mar 2011, Josue Abarca wrote:
> What about?:
>
> From: /usr/share/doc/autotools-dev/README.Debian.gz
> "Example autogen.sh and debian/rules files can be found in
> /usr/share/doc/autotools-dev/examples. Do not use them as-is. Rather,
> properly customize your own."
And look at the dat
On Tue, 15 Mar 2011, Julien Cristau wrote:
> On Tue, Mar 15, 2011 at 17:52:31 +0100, Bernd Zeimetz wrote:
> > And for packages you either have to do stable updates all the time, or
> > add an additional repository, or use unstable on a server. Whatever you
> > prefer.
> >
> Not to mention debian m
Am 16.03.2011 17:36, schrieb Ian Jackson:
> Vincent Danjean writes ("Re: Best practice for cleaning autotools-generated
> files?"):
>
>> So Makefile rules can then re-run auto* tools at build time and you
>> lost the benefit you want to have.
>
> Makefile rules should not rerun auto* stuff at bu
Vincent Danjean writes ("Re: Best practice for cleaning autotools-generated
files?"):
> On 16/03/2011 14:59, Ian Jackson wrote:
> > I think this is bad advice. These files should be shipped in the
> > source package.
> >
> > Doing that makes it much easier to build the package in unexpected
>
* Vincent Danjean [110316 15:48]:
> Then, you need a way to patch them. There is lots of software where
> you need to patch configure.ac and/or Makefile.am
Having to patch something and having to patch nothing are two very
different cases.
It usually also make sense to think twice before patchin
On Tue, Mar 15, 2011 at 10:29:57PM +, Marcin Owsiany wrote:
> The current best practice for dealing with packages using GNU autotools
> (as described in /usr/share/doc/autotools-dev/README.Debian.gz) is to
> run autoreconf in a prerequisite of a build target, and to remove its
> results in the
On Wed, Mar 16, 2011 at 01:07:19AM +0100, Goswin von Brederlow wrote:
> Roger Leigh writes:
>
> > On Mon, Feb 28, 2011 at 03:36:47PM +0100, Wouter Verhelst wrote:
> >> On Tue, Feb 22, 2011 at 05:08:18PM +, Roger Leigh wrote:
> >> > On Mon, Feb 21, 2011 at 07:42:32PM -0600, Raphael Geissert wr
On 16/03/2011 14:59, Ian Jackson wrote:
> Marcin Owsiany writes ("Best practice for cleaning autotools-generated
> files?"):
>> The current best practice for dealing with packages using GNU autotools
>> (as described in /usr/share/doc/autotools-dev/README.Debian.gz) is to
>> run autoreconf in a pr
Goswin von Brederlow writes ("Transitional packages with conffiles"):
> Looking into the cause we discovered that the problem is that
> dhcp3-client is now a transitional package that pulls in
> isc-dhcp-client. The new package expects its config files in /etc/dhcp
> while the old had /etc/dhcp3/.
Marcin Owsiany writes ("Best practice for cleaning autotools-generated files?"):
> The current best practice for dealing with packages using GNU autotools
> (as described in /usr/share/doc/autotools-dev/README.Debian.gz) is to
> run autoreconf in a prerequisite of a build target, and to remove its
* Goswin von Brederlow [110316 01:24]:
> I disagree. If non-free has a superior implementation of a package and
> the user has non-free configured then it should prefer the non-free
> package.
Superiority is always a question of what metrics you start with.
Not being able to fix bugs because of m
* Marcin Owsiany [110315 23:30]:
> The current best practice for dealing with packages using GNU autotools
> (as described in /usr/share/doc/autotools-dev/README.Debian.gz) is to
> run autoreconf in a prerequisite of a build target, and to remove its
> results in the clean target.
Well, here I ne
On Tue, 15 Mar 2011 23:35:59 +
Ben Hutchings wrote:
> On Tue, Mar 15, 2011 at 10:55:54PM +, Neil Williams wrote:
> > Other tools, like svn-buildpackage, don't have this problem, via the
> > mergeWithUpstream support and/or a ../tarballs/ directory. Not perfect
> > but it works.
> [...]
>
On Tue, Mar 15, 2011 at 10:29:57PM +, Marcin Owsiany wrote:
> * maintain a whitelist of distributed files, and "rm" everything
>else (apart from the debian directory) in the clean target.
>
>Since I use (or plan to use) git-buildpackage, I don't have a tarball
>which could serve a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-03-15 23:55, Neil Williams wrote:
> Using autotools with Debian native packages can be a real PITA and
> source format 3.0 just gets it wrong mostly. Most other tools also get
> it wrong, even svn-buildpackage. If I knew how to fix it reliabl
Just wanted to point out as a user that the current system needs to work
also as some isp offer free access mirrors or a mirror groups, ie
partner isp's mirrors that are also part of `free usage`.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe".
23 matches
Mail list logo
