aboutsummaryrefslogtreecommitdiffstats
path: root/debian/rules
Commit message (Collapse)AuthorAgeLines
* Avoid 'dpkg-buildflags --export=configure, since it doesn't exist in squeeze.Jelmer Vernooij2014-09-27-2/+8
|
* Allow LDFLAGS to be provided in the environment and consistently use $(LDFLAGS)Jelmer Vernooij2014-07-20-1/+1
| | | | | when linking (not partially linking).
* Pass dpkg-buildflags to actual configure command.Jelmer Vernooij2014-07-20-1/+1
|
* Force re-building of user guide on Debian.Jelmer Vernooij2014-07-20-0/+1
|
* Build with dpkg-flags, for hardening.Jelmer Vernooij2014-07-20-1/+1
|
* Two small fixes to make Debian builds work again.Wilmer van der Gaast2014-07-01-1/+1
|
* Removing the version number override hack broken by a recent NMU. Instead,Wilmer van der Gaast2011-12-23-4/+0
| | | | | I'll try to solve this problem on just the buildbot using "dch".
* Merging Debian 3.0.3-1.1 changes.Wilmer van der Gaast2011-12-20-3/+3
|
* Build skyped as arch=all, and don't build it by default. Debian has removedWilmer van der Gaast2011-12-20-2/+6
| | | | | the python-skype package.. :-(
* Another packaging fix: Don't put skyped manpage in bitlbee-common.Wilmer van der Gaast2011-12-11-0/+3
|
* Skype module packaging.Wilmer van der Gaast2011-12-10-2/+11
|
* Actually, let's also drop the -0.Wilmer van der Gaast2011-04-22-1/+1
|
* Don't put an epoch in the Debian "spoofed" version number. Debian's nowWilmer van der Gaast2011-04-22-1/+1
| | | | | | | | | | | | | | | | | | | barfing on the "1:bzr-devel-xx" version numbers generated by the nightlies builder (due to "bzr" not being a number) so I have to think of something else. The main reason for using epochs was so "bzr-devel-xx" will be considered newer than "3.0.2". ASCII-wise this should be the case even without epochs but okay, it made sense to do this anyway to avoid apple-orange comparisons. Now I'll try switching to package version numbers like 3.0.2+devel+xx-0. No need for epochs then, plus 3.0.3 will actually win over 3.0.2+devel+xx-0 when it should. This does probably mean that people who still have 1:bzr-something installed won't be upgraded automatically, I guess I'll try to let everyone know via Twitter, etc..
* Added lintian overrides for bitlbee & bitlbee-libpurpleأحمد المحمودي (Ahmed El-Mahmoudy)2010-10-25-0/+1
|
* Added Debian packaging for OTR plugin. It's built by default but this canWilmer van der Gaast2010-10-09-10/+14
| | | | | be disabled by setting BITLBEE_OTR to 0 (or 1 to compile it into the binary).
* Pass the -Npackage flag the right way so bitlbee-libpurple doesn't appearWilmer van der Gaast2010-08-18-7/+7
| | | | | in debian/files. The previous hack broke genchanges/debsign.
* Move scripts, debconf and /etc stuff to bitlbee-common and really haveWilmer van der Gaast2010-08-18-12/+7
| | | | | | *just* the binary in bitlbee{,-libpurple}. This should fix issues with installing the package on a clean machine.
* Debian change: set BITLBEE_LIBPURPLE=0 to only build the native variant.Wilmer van der Gaast2010-08-17-5/+15
|
* Make the "chop off +b stuff from version number" more specific to match justWilmer van der Gaast2010-07-30-1/+1
| | | | | binary NMUs.
* Some more fixes to make this work with older distros (Hardy's stuck withWilmer van der Gaast2010-06-06-3/+5
| | | | | | debhelper 6) and on de code.b.o build bot (a substvars file I wasn't using anymore caused troubles).
* Make this build work even from fresh bzr branches. Also stop using {x,y}Wilmer van der Gaast2010-06-06-1/+3
| | | | | stuff which somehow magically doesn't work on my laptop.
* Put in the necessary hacks to make version number spoofing work again.Wilmer van der Gaast2010-06-05-5/+6
|
* Remaining fixes: All looks good now, apt and dpkg seem to do the rightWilmer van der Gaast2010-06-05-4/+8
| | | | | thing with the -common transition, etc.
* Redid debian/rules using debhelper, with good results. This creates mostlyWilmer van der Gaast2010-06-05-89/+74
| | | | | | fine debs. Need to do some more checks, and make sure bitlbee-libpurple gets the same maintainer scripts as bitlbee.
* Merging stuff from mainline (1.2.6).Wilmer van der Gaast2010-04-24-1/+1
|\
| * Also override package version number for bitlbee-dev when $BITLBEE_VERSIONWilmer van der Gaast2010-04-24-1/+1
| | | | | | | | | | is set.
* | Added BITLBEE_CONFIGURE_FLAGS variable so configure flags can be overriddenWilmer van der Gaast2010-04-24-1/+2
|/ | | | | when generating debs.
* Uploaded 1.2.2-1. Now patching up bitlbee.conf at build time to keep1.2.2-1Wilmer van der Gaast2008-08-28-0/+1
| | | | | bzr/upstream separated from the Debian package.
* Stop ignoring distclean exit code.Jelmer Vernooij2008-06-16-1/+1
|
* Added bitlbee-dev package, finalized 1.2-4 package.1.2-4Wilmer van der Gaast2008-05-07-11/+33
|
* Removed DEB_BUILD_OPTIONS because it turns out this isn't just some string1.2-3Wilmer van der Gaast2008-03-24-1/+1
| | | | | | | I can pass through to configure, there's an official policy on what can be in there exactly. (Or at least I found a suggested policy on the debian- policy mailing list.) 1.2-3, because I just uploaded -2 already. :-(
* Updated/Fixed Debian package.1.2-1Wilmer van der Gaast2008-03-21-3/+6
|
* Adding an epoch to "spoofed" version numbers to make sure apt doesn'tWilmer van der Gaast2007-07-14-1/+1
| | | | | stick with distro packages.
* Adding debian/ tree to the repository again. Updated it to include allWilmer van der Gaast2007-07-06-0/+83
| | | | | | 1.0.x versions and some other changes. Might soon start building snapshots again. :-)
* Let's not keep debian/ in bzr.Wilmer van der Gaast2005-11-09-100/+0
|
* Initial repository (0.99 release tree)0.99Wilmer van der Gaast2005-11-06-0/+100
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-19 18:49:45 +0000