On Tuesday 23 of August 2011, Caleb Maclennan wrote:
> What's the deal there? Are we happily patching up a dinosaur? What's
> the barrier to moving to one of the newer branches?
Lack of working spec with rpm from these branches. Only that. W would also
switch to newer berkeley db then.
--
Arka
On Tue, Aug 23, 2011 at 19:14, Patryk Zawadzki wrote:
> Yes, other rpm wrappers support triggers. I think the proper way would
> be to add these to rpm itself rather than trying to hack them into
> poldek.
Add add system wide %pre-transaction %post-transaction macros to rpm
itself? That sounds fa
On Tue, Aug 23, 2011 at 6:10 PM, Caleb Maclennan wrote:
> On Tue, Aug 23, 2011 at 17:54, Patryk Zawadzki wrote:
>> If you're only interested in a particular
>> group of packages, consider faking install-time expansion by calling a
>> common shell script in %post or %posttrans.
> I am interested i
On Tue, Aug 23, 2011 at 17:54, Patryk Zawadzki wrote:
> If you're only interested in a particular
> group of packages, consider faking install-time expansion by calling a
> common shell script in %post or %posttrans.
I am interested in ALL packages, however I don't understand what you
mean by "fa
On Tue, Aug 23, 2011 at 4:44 PM, Caleb Maclennan wrote:
> Does poldek offer any hooks or way to trigger actions at any point?
> For example are there pre/post transaction hooks that I could modify
> to run something before and/or after any rpm action is taken? How
> about an "on exit if any packag
Does poldek offer any hooks or way to trigger actions at any point?
For example are there pre/post transaction hooks that I could modify
to run something before and/or after any rpm action is taken? How
about an "on exit if any package installed / upgraded / uninstalled"
during the lifetime of the
