(pinfo for instance)
So that should be added to the transition plan.
--
Nathanael Nerode <[EMAIL PROTECTED]>
"It's just a goddamned piece of paper."
-- President Bush, referring to the US Constitution
http://www.capitolhillblue.com/artman/publish/article_7779.shtml
--
more likely, given its contents, multiple libraries), with a single
purpose, and a public, exported interface providing well-documented utilities
for
that purpose. Since this hasn't happened in the long time dpkg has been
developed, however, I suspect that there's a fundamental
OK. So I managed to construct a dselect source package which builds
independently of dpkg. It required duplicating substantial portions of
lib/ . I intend that to be temporary. Until those portions are gone,
I will keep an eye on any changes made to lib/ in dpkg.
My plan for dselect is to make
a trigger" ('consumer' or 'switchboard'). That
was
the only confusing part of reading this; it didn't make sense until after I got
to the examples (and read the rest of it with those terms in mind).
Perhaps "triggering package" and "trigger-implementing
, $dirfile, $!));
- unlink("$dirfile.lock") ||
- die sprintf(_g("%s: unlock %s: %s"), $name, $dirfile, $!)."\n";
+if (!$nowrite) {
system ('cp', $dirfile, $backup) &&
- warn sprintf(_g("%s: couldn't backup %s in %s: %s"), $name, $dirfile,
$backup, $!)."\n";
+ warn sprintf(_g("%s: couldn't backup %s in %s: %s"), $name, $dirfile,
$backup, $!)."\n";
}
sub ulquit {
-unlink("$dirfile.lock") ||
- warn sprintf(_g("%s: warning - unable to unlock %s: %s"),
-$name, $dirfile, $!)."\n";
die "$name: $_[0]\n";
}
--
Nathanael Nerode <[EMAIL PROTECTED]>
[Insert famous quote here]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ndency; I believe all the necessary functionality is present in 5.8.4
(which
is in 'stable'); I'm just not 100% sure.
This is copyright-worthy content, so here's my copyright notice for
debian/copyright
(should you choose to apply this patch):
Copyright 2006 Nathanael Nerode
[EMAIL PROTECTED] wrote:
> -working with arch seems somewhat risky at the moment. I'm not sure
> we're all very comfortable with these distributed RCS and this
> currently raises a quite high barrier to people who want to
> contribute.
Arch (as currently used by dpkg, anyway) *does* raise an unn
Christain Perrier wrote:
>I think that we will probably propose to completely abandon dselect
>after etch release.
Please don't. Some of us are very happy with dselect and still don't consider
aptitude a usable replacement.
If dselect ever manages to get broken out into a separate source packa
Scott James Remnant:
> I don't
> consider old bugs to be worthy of discard,
You mean, "I don't consider unreproducible bugs to be worthy of discard,"
right? Old reproducible bugs (like 2531, the third oldest open bug in
Debian) are one thing and they should certainly be kept.
Incidentally, co
Scott James Remnant wrote:
>I've already done this; all the open bugs are known bugs.
Really? This seems extremely unlikely given the state of the bug reports.
Consider 52087.
Well then, a lot of tag changes are necessary.
96813: tagged unreproducible
198699: tagged unreproducible
172752: tagged
Is it OK if I go through the antique bugs in dpkg (older than oh, say, 2002)
and close the ones which are
(a) unreproducible
or
(b) appear to clearly apply only to versions from before 'woody' (<<1.9.21)
This would render the bug list significantly more meaningful.
--
Nathanael
Blrgh!
OK. So I was working on the problem of fixing dpkg-dev so that
foo Depends: foo-data {SourceVersion}, foo-libs {BinaryVersion}
or something similar actually works. By parsing the version numbers.
Now it's apparently been changed under our noses, in such a way that my
proposed
sch
That is actually buggy. In case the Debian version is
"-1.0.1" your code would produce "-1.0", but the correct result would be
"-1".
Um, yes, and I can fix that.
Can we decide on the naming issue (which one gets the "Source-Version"
name) before I submit a fixed patch? :-)
I guess I've got m
$substvar{'Source-Version'} =~ s/(-[\d+]+\.[\d+]+)\.[\d+]+$/$1/;
+# Leave this for strict binary version dependencies.
+$substvar{'Binary-Version'}= $fi{"L Version"};
}
--
Nathanael Nerode <[EMAIL PROTECTED]>
"(Instead, we front-load
I'm beginning to wonder if dpkg is actually maintained at all.
What the heck is going on here?
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
I believe that the ancient bug 6039
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=6039) against dselect
is fixed by the existence of the 'apt' backend to dselect, which
apparently does everything the submitter wanted it to. :-)
Could someone please confirm that this is fixed, and close the
Just update the Conflicts already.
17 matches
Mail list logo
