Differences between revisions 2 and 3
Revision 2 as of 2017-01-01 16:58:54
Size: 735
Editor: GuillemJover
Comment: Rename to a more neutral name, defect reads too assertive and objective, when many points are going to be subjective
Revision 3 as of 2017-01-01 17:04:15
Size: 997
Editor: GuillemJover
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Teams/Dpkg/SourceFormatDefects
This page intends to track any possible design defect in the current source formats, so that they can be taken into account when and iff we decide to create a new source format. Some of these defects might be purely subjective based on different workflows or different views of how source packages or source distributions are to be handled. But just as well, we might list anything that might potentially put people off the current source formats.
This page intends to track any possible design problem, limitation and defect in the current source formats, so that they can be taken into account as things with higher priority to fix or when and iff we decide to create a new source format. Some of these problems might be purely subjective based on different workflows or different views of how source packages or source distributions are to be handled. But just as well, we might list anything that might potentially put people off the current source formats.
Line 7: Line 6:

== Issues with 3.0 (native) ==

 * People want the ability to use a non-native version for a native package, for some workflows, which hints at limitations in the tooling and similar instead of allowing this incongruency (expand). DebianBug:737634

This page intends to track any possible design problem, limitation and defect in the current source formats, so that they can be taken into account as things with higher priority to fix or when and iff we decide to create a new source format. Some of these problems might be purely subjective based on different workflows or different views of how source packages or source distributions are to be handled. But just as well, we might list anything that might potentially put people off the current source formats.

Issues with 3.0 (quilt)

Issues with 3.0 (native)

  • People want the ability to use a non-native version for a native package, for some workflows, which hints at limitations in the tooling and similar instead of allowing this incongruency (expand). 737634