> Note that the subpackages approach has a problem if an extra goes away and it
> was installed on user machine.
Maybe not a *huge* concern... setuptools' documentation tells developers not to
do that.
Ok, this should be it. I am going to squash all but the first patches into one
after review.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
ffesti commented on this pull request.
> + rpmlog(RPMLOG_ERR, _("line %d: Bad option %s: %s\n"),
+ spec->lineNum,
+ poptBadOption(optCon, POPT_BADOPTION_NOALIAS),
+ spec->line);
+ goto exit;
+}
+
+lst = argvNew();
+
+for (arg = 1; arg
@ffesti pushed 1 commit.
088636d631850bd91bdd267d8f96bc568596ef04 Use popt to properly parse the
arguments of %patchlist and %sourcelist
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
I can live with macrobody, a little bit of name-spacing never hurt anybody.
In the meanwhile, I'm starting to think it does need to expand its argument
like everything else, this is too limiting. Ie it'd still take a macro name as
an argument, but that the name can come from a macro instead of
Okay, at least someone thinks this would be useful, so I guess it makes it
worth pursuing :slightly_smiling_face:
The implementation here is a icky and slow as it has to go backwards and out of
its way to reconstruct what grabArgs() had readily available, probably
grabArgs() just needs to
Right, I'm by no means opposed to this, and integrating with rpmdb is certainly
the way to go, rather than strange external tools. Was just curious about the
concrete difference.
Can you update the commit message to elaborate a bit on how it works and
possible side-effects, at least that part
@mlschroe pushed 1 commit.
dd4bb9f38fdf1d147a09ca0cdbf38ed75e409b17 Add a --salvagedb option to the rpmdb
tool
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
I'd prefer if we named this %macrobody, so that there's less chance that it
clashes with somebody else's use of %body.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Merged #1067 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1067#event-3029980388___
Rpm-maint mailing list
No, there's a (very) small chance that it picks up entries that have been
deleted. It's like the .recover command of the sqlite cli:
Like the ".dump" command, ".recover" attempts to convert the entire contents of
a database file to text. The difference is that instead of reading data using
the
Those incidents are probably related:
http://lists.rpm.org/pipermail/rpm-list/2020-February/002011.html
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
12 matches
Mail list logo
