Closed #628 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/628#event-11095975641
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mai
I had yet another look at this and it seems just as unfeasible as it always did:
- The vast majority of commands in scriptlets lack absolute paths, so it emits
executable(fu), which would need packages to provide the basenames of all their
executables to match these, which can cause wrong package
I do think this could be useful if it would serve to reduce packager workload,
though the trend seems to be moving away from scriptlets in general.
--
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-softw
I never asked you to implement it :)
I try to always open an issue and discuss whether it is something which we
would get in before doing the actual implementation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://gi
Mind you, the above doesn't mean I wouldn't consider a nice patch adding
support for scriptlet dependency autogeneration: from bash --rpm-requires
output, at least "executable(/absolute/path)" entries should be more-or-less
safely usable after just mangling them to regular file dependencies. It'
Look, I've poked at it several times over the years. Unless there's been some
major advances in that department, it's just more trouble than its worth.
--
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-
@pmatilai for the simple scriptlets which call ldconfig or anything else simple
(few commands), I think using `bash --rpm-requires` would be more than enough
and will be more nice to users so they don't have to write `Requires(post):
/usr/sbin/semanage` or anything like that.
--
You are receiv
Um, what? The stuff removed in that commit had never been used at all in rpm,
and scriptlet dependency extraction has never been implemented, much less
removed.
I know about bash --rpm-requires, but the results you get are so far off that
it's more trouble than actually helping anything.
--
Y
It seems that b780f5a8d636073d67dbcdfa3f8795f878b55218 (from 2007) removed such
generator as not being used which probably happened because it was not ported
to new dependency generators syntax or so.
It would be nice if we could generate dependencies on scriptlets using that
code. No more Requ