Re: [gentoo-portage-dev] recent changes in the way pkgsplit() and company work

[Zac Medico]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

dol-sen@×××××.net wrote:
>
> Sorry, but I didn't have an internet connection for January to notice but when I
> upgraded to 2.1.2-r7 pkgsplit, catpkgsplit, catsplit no longer accepted ebuild
> strings with any atoms.  Porthole was crashing in several places.

Some of the functions are more strict than they used to be about
invalid dependency data.  If portage_dep._dep_check_strict = False
is set then the new strict behavior will be disabled.  Note that
portage will now refuse to install packages with invalid dependency
data.  The strict behavior is only disabled when dealing with
installed packages.  Eventually, it should be possible to keep the
strict behavior enabled at all times.

> I have changed portholes coding to work around it, but there are several more
> bugs for me to fix before considering it for a new release (a few unfinished
> features too).  My main question is what approximate time frame is if any being
> considered for stabilizing the 2.1.2 version.  I will need to make sure I have a
> release ready for porthole users.

Actually, I was planning to open a stabilization bug tomorrow
morning.  Soon the tree snapshot will be taken for the 2007.0
release media, so we really need to have the arch teams stabilize it
quite soon.

Zac

> Also, I had copied a little code from gentoolkit which also puked at the change
> in strictness.  I don't know if that has been changed already.  It was in
> split_package_name().  It was called from find_best_match() called from
> get_system_pkgs().
>
> Brian
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)

iD8DBQFFyYqn/ejvha5XGaMRAq75AKCj2Milssa087pLkxH6lTIIGsEnvgCfaxMh
1LR+FJCEkITtRCQrvE+Glmk=
=lbU1
-----END PGP SIGNATURE-----
-- 
gentoo-portage-dev@g.o mailing list