Hi Sean,
I finally got around to reviewing your patch to maintain the conffile
database during unpack/configure/remove stages. I am still worried
that the “commit” operation does not seem to be atomic like it should
be. Could you look at my description of your patch and let me know
where I go
Tollef Fog Heen tfh...@err.no writes:
]] Goswin von Brederlow
| Remove 3.0 (qit) format completly. A full history bloats the source
| and a cut down history has no advantage over a plain source.
I think this would be a mistake. I'm increasingly considering a full
git clone the source of
hi jonathan,
thanks for your feedback on this and the previous patches.
before going any further, i'd like to point out that i'm still waiting
for feedback from guillem, and i don't plan on doing any further work
on this until i hear at least something from him indicating that he's
interested
Goswin von Brederlow goswin-...@web.de writes:
Tollef Fog Heen tfh...@err.no writes:
I think this would be a mistake. I'm increasingly considering a full
git clone the source of my software (in the «preferred form of
modification») and so having dpkg able to natively consume and produce
I support changing 3.0 (git) to use a bundle. Besides closing the bugs
mentioned in this thread, a bundle consists of a simple header + a standard
git pack. Since git packs are used as a wire format, this provides better
assurance that future versions of git will retain compatability with
the
Package: dpkg-dev
Version: 1.14.25
Severity: normal
libcgi-application-basic-plugin-bundle-perl is a package that aggregates
several Perl modules from CPAN (each of these is distributed upstream as
a .tar.gz)
What I currently do is to include these modules within in a
tarballs subdirectory
6 matches
Mail list logo
