On Wed, Oct 15, 2014 at 12:41:19PM -0400, Joey Hess wrote:
> Mikko Rapeli wrote:
> > I have fought this issue for years. Build a package and then try to fix
> > some bugs locally. Silly bugs like bad .install or package scripts should be
> > straight forward to fix without complete rebuild of the p
Mikko Rapeli wrote:
> I have fought this issue for years. Build a package and then try to fix
> some bugs locally. Silly bugs like bad .install or package scripts should be
> straight forward to fix without complete rebuild of the package,
> which can take hours, or even days on smaller machines. I
On Wed, Oct 15, 2014 at 10:08:15AM -0400, Joey Hess wrote:
> Mikko Rapeli wrote:
> > debhelper build status log file is not documented in manual pages.
> > Common developer use cases involve modifying list of installed files
> > and package install scripts, and for these use cases a complete re-com
Mikko Rapeli wrote:
> debhelper build status log file is not documented in manual pages.
> Common developer use cases involve modifying list of installed files
> and package install scripts, and for these use cases a complete re-compile
> of the packages in not necessary. Instead developers could m
4 matches
Mail list logo