Simon Stelling wrote:
> Hey all,
>
> I'm just wading through a list of ~200 bugs of which
some need decisions
> what
> should be done, whether it should be done at all or
simply whether it is
> a bug
> or not.
>
> Bug: SRC_URI: spaces not supported
> http://
bugs.gentoo.org/show_bug.cgi?id=102607
> Is this a 'NOTABUG' case?
Need to check the SRC_URI documentation, if it's noted
there, then close
it, if its not noted in the docs, add that spaces are not
allowed and
close it ;)
>
> Bug: gpg: "strict" incorrectly takes
priority over "severe"
> http://b
ugs.gentoo.org/show_bug.cgi?id=68906
> What's the expected behaviour? Is it NOTABUG?
>
> Bug: Method to monitor a package without
installing/upgrading it
> http://b
ugs.gentoo.org/show_bug.cgi?id=47456
> Same thing. Do we want this?
>
Alternative tool.
> Bug: Support for a pre-compile pkg_config
> http://b
ugs.gentoo.org/show_bug.cgi?id=99529
> As Jason mentioned: Is this worth the effort?
Effort is minimal, but I'm unsure of the real usefulness.
>
> Bug: per profile package.keywords
> http://b
ugs.gentoo.org/show_bug.cgi?id=55321
> Voting seems to be a bit... incomplete ;)
This is down to a design issue. package.keywords is a
repository
control measure, do we currently allow profiles to mess with
repos?
Only via use.mask at present. profile mangling of a
repository is
difficult when multiple repositories are brought in because
we really
don't have any type of repo binding in the current source.
I personally
think it's an important feature, but it's difficult to not
implement it
in a half assed manner.
>
> Bug: Wording "These are the packages that I would
merge, in order:"
> http://
bugs.gentoo.org/show_bug.cgi?id=112439
> This needs a decision too. What wording do we prefer?
Either way, the
> bug should
> be closed, the fix is trivial in case we want to change
it.
Ummm someone just make a decision, I don't think it's that
big a deal.
>
> Bug: global exception handling
> http://b
ugs.gentoo.org/show_bug.cgi?id=28535
> Should tracebacks be thrown in the users' face or not?
>
Yes, Not saying you shouldn't write code that catches
exceptions and all
that but writing stupid code that catches any exception and
then tries
to print some useful info is...not as useful. I'd prefer
to have
documented a bit more what functions throw ( docstrings )?
so that when
users use portage functionality they know what to catch.
> Bug: /usr/lib/portage/bin/clean_locks documentation
example could make
> use use
> DISTDIR
> http://
bugs.gentoo.org/show_bug.cgi?id=116676
> Call portageq or not? Voting time ;)
nfc :0
>
> That should be enough for the moment. More will
probably follow,
> considering
> that I only checked the first 60 bugs or so :/ It would
be nice if we
> could make
> the needed decision and then close the bugs where it is
> NOTABUG/INVALID/LATER. I
> hate stale bug listings ;)
>
--
gentoo-portage-dev gentoo.org mailing list
|
Bug: Support for src_test deps required