1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
General ToDo list for emdebian-tools
====================================
(no particular order, the numbers are chronological of the
appearance of the issue.)
emdebuild bug:
==============
1. create a way to replicate the apt-cross dependency list, just
as an informative list. Link that with empath. (Replace with debian/xcontrol)
(note for website, not emdebian-tools)
2. Incorporate build success|failure output into search.php - when
clicking on a dependency, if the build failed show the build log.
3. libtool problems: copy the relevant files from the extracted source package
to a temporary dir, configure libtool, build a test library.
4. emsource could do with using libsvn-perl
5. advise users to switch to static IP addresses to get things like
USB networking enabled - network-manager tries to access the
internet via the balloon USB connection which is plain stupid.
9. emdebuild to override debian/control Build-Depends with debian/xcontrol
Build-Depends.
10. em_make and emsource to wrap unwanted rules in nodocs or nocheck
to aid preparation of a patch for upstream - easier updates.
11. update method: patch $package.old/$file, diff .old against updated Debian
file, apply diff to $file to generate emdebian patch file, refresh emdebian
patch file with emdebuild.
12. Allow debian/copyright into the package - remove with dpkg filtering when available.
(Needs debhelper assistance)
13. apt-cross to hack around limitations of debootstrap with multiple mirrors.
Reinventing so look into Stag again.
14. apt-key add requires a recent date - stops emsecondstage.
15. codehelp, ideally we'd have a pile of workarounds, and switches to turn them off, so we can have working packages and automated testing of whether a package actually needs them
<codehelp> I can do that
(this is done in 0.7.3)
<WorkingGeier> the idea would be to talk to jvw
<codehelp> I built four packages before I found one that needed the libtool hack
jvw?
who's that? (excuse my ignorance)
<WorkingGeier> Jeroen van Wolfelaar
he wrote a system called Mole during SoC
which allows us to track dynamic info about packages
i.e. autobuilder results, testsuite runs etc
we could hook into that, and have warnings "your package needs the following kludges to autobuild" to the PTS pages
s/to/on/
<codehelp> yes, I know mole - I know who you mean now. Thanks
'[X-]Build-Cross-Libtool: yes'
16. emtargetcmp needs to handle binNMU versions: 0.125+b1 as equal to the equivalent source:Version.
|
