[arch-dev-public] devtools problem

Pierre Schmitz pierre at archlinux.de
Wed Mar 16 17:37:02 EDT 2011

On Wed, 16 Mar 2011 16:24:42 -0500, Dan McGee wrote:
> On Wed, Mar 16, 2011 at 4:21 PM, Pierre Schmitz <pierre at archlinux.de> wrote:
>>>> I guess to solve the first problem we would
>>>> also need a pacman-db-downgrade script.
>>> pacman-db-downgrade would be basically impossible...  you could
>>> symlink the desc file to depends in every local package database
>>> directory.
> I'm not following the logic in this thread at all. Won't this be a
> problem for all of like 3 days here when the pacman version in
> [testing] vs. non-testing is different? And after that who cares? Or
> you could just upgrade your chroots and system to pacman 3.5 and it
> wouldn't matter either; this package depends on nothing else in
> [testing].

Sure, if it wont be in testing for weeks we should just ignore the
problem as it will fix itself once this is in [core].

>> If I'd add those link pacman 3.4 would be able to read the db, right?
>> But once we update to 3.5 the upgrade script will ad all entries again.
>> Maybe I'll need to modify the upgrade script to remove the desc files if
>> they are just links.
>> Btw: Do you guys plan the same for the db files? (merging deps and desc
>> entries)
> Eventually, but there is this crazy thing called backward
> compatibility that we have to take into account...

But that's only a temporary issue. :-)

Pierre Schmitz, https://users.archlinux.de/~pierre

More information about the arch-dev-public mailing list