* Marco d'Itri:
It is not mandatory to fully rebuild a package every time the Debian
binary package is generated, and in some cases it may be impractical
and undesirable, but the following issues must be considered:
- the package must contain source for all components, otherwise it would
[EMAIL PROTECTED] wrote:
- the release manager (and probably the security team as well) must be
comfortable with the result
And the package should state *which* tool is required to rebuild the
package. 8-/
This is why I mentioned the last condition, the build process should be
fully automatic
[EMAIL PROTECTED] wrote:
Must packages in main derive the contents of binary packages from the
sources shipped in the source package, or can they simply copy
pre-generated, not directly editable files which have been derived
using some other process (not available in the package sources)?
I
Must packages in main derive the contents of binary packages from the
sources shipped in the source package, or can they simply copy
pre-generated, not directly editable files which have been derived
using some other process (not available in the package sources)?
--
To UNSUBSCRIBE, email to
On Wed, 03 Dec 2008 11:27:14 +0100, Florian Weimer wrote:
Must packages in main derive the contents of binary packages from the
sources shipped in the source package,
Yes.
or can they simply copy pre-generated, not directly editable files which have
been derived using some other process
On Wed, Dec 3, 2008 at 7:27 PM, Florian Weimer [EMAIL PROTECTED] wrote:
Must packages in main derive the contents of binary packages from the
sources shipped in the source package, or can they simply copy
pre-generated, not directly editable files which have been derived
using some other
* Paul Wise:
On Wed, Dec 3, 2008 at 7:27 PM, Florian Weimer [EMAIL PROTECTED] wrote:
Must packages in main derive the contents of binary packages from the
sources shipped in the source package, or can they simply copy
pre-generated, not directly editable files which have been derived
using
On Wed, Dec 3, 2008 at 7:42 PM, Florian Weimer [EMAIL PROTECTED] wrote:
libjs-jquery prompted this question. The files in dist/ have been
processed and are not source-equivalent, and are directly copied into
the binary package.
Quite a common occurrence with JavaScript stuff unfortunately.
On Wed, Dec 3, 2008 at 8:29 PM, Paul Wise [EMAIL PROTECTED] wrote:
Build the packed javascript in debian/rules using the yahoo compressor
(or another).
Looks like this is planned already:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495178#10
--
bye,
pabs
Paul Wise wrote:
[...]
Build the packed javascript in debian/rules using the yahoo compressor
(or another).
That reminds me of a bug in one of the js-related packages which resulted in the
switch from the compressed to the uncompressed .js due to bad compression
causing errors.
That's a
10 matches
Mail list logo
