On 25 June 2011 00:51, Nathan Phillip Brink bi...@gentoo.org wrote:
On Wed, Jun 22, 2011 at 11:20:40PM -0400, Wyatt Epp wrote:
I bring this up because there are several packages with the same name
and different qualification. Obviously, they'll have different tags
because they're not the same
On 25 June 2011 00:57, Nathan Phillip Brink bi...@gentoo.org wrote:
On Wed, Jun 22, 2011 at 08:57:47PM -0400, Wyatt Epp wrote:
cat
tagmedia/tag
tagvideo/tag
tagkde/tag
tageditors/tag
/cat
I'm strongly of the mind that by making the tag system arbitrarily
flat, you might be prematurely
On 6/24/11 11:35 PM, Michał Górny wrote:
Hello,
git-2.eclass is in the tree for a while now, and there's still awful
lot of packages using old deprecated git.eclass.
Why migrate?
Hi,
What are the pitfalls during migration? Or is it just /git/git-2/ ?
Thanks jusitn
signature.asc
Hi,
I was signing my commits since I am a dev, but I just discovered that I
only do sha1 signing. How do I switch to sha256 signing?
justin
signature.asc
Description: OpenPGP digital signature
On Sat, 25 Jun 2011 09:11:16 +0200
justin j...@gentoo.org wrote:
On 6/24/11 11:35 PM, Michał Górny wrote:
Hello,
git-2.eclass is in the tree for a while now, and there's still awful
lot of packages using old deprecated git.eclass.
Why migrate?
What are the pitfalls during
On Sat, 25 Jun 2011 09:37:55 +0200
justin j...@gentoo.org wrote:
I was signing my commits since I am a dev, but I just discovered that
I only do sha1 signing. How do I switch to sha256 signing?
$ grep digest ~/.gnupg/gpg.conf
personal-digest-preferences sha256,sha512,sha1,ripemd160,md5
--
On 06/25/2011 12:35 AM, Michał Górny wrote:
Hello,
git-2.eclass is in the tree for a while now, and there's still awful
lot of packages using old deprecated git.eclass.
I think I remember seeing deprecation warnings in the past when an
ebuild was using a deprecated eclass (right at the
On Sat, Jun 25, 2011 at 02:49, Kent Fredric kentfred...@gmail.com wrote:
I'm strongly of the mind that by making the tag system arbitrarily
flat, you might be prematurely limiting yourself, as well as risking a
future where the tag index is a sea of meaningless words.
Tags in my mind, should
On Tuesday 21 of June 2011 16:24:07 Michał Górny wrote:
Hello,
As we discussed for a while, the media-sound/ category has grown very
large and it may be a good idea to split it.
Right now, it contains audio players, editing software, converters,
sound systems and a lot of other utilities
On Friday 24 of June 2011 09:55:19 Ciaran McCreesh wrote:
On Fri, 24 Jun 2011 09:52:03 +0200
Jesús J. Guerrero Botella jesus.guerrero.bote...@gmail.com wrote:
You might not like it, but Gentoo categories have always been
directories, not words into metadata.xml.
So tags are in some way
On 25 June 2011 23:55, Maciej Mrozowski reave...@gmail.com wrote:
IMHO the best approach is to forget about categories and:
- make package names unique identifiers (it's not that hard, renaming stuff in
app-xemacs mostly) - categories would serve no purpose as id anymore (though
may need to
On Sat, 25 Jun 2011 13:55:40 +0200
Maciej Mrozowski reave...@gmail.com wrote:
On Friday 24 of June 2011 09:55:19 Ciaran McCreesh wrote:
On Fri, 24 Jun 2011 09:52:03 +0200
Jesús J. Guerrero Botella jesus.guerrero.bote...@gmail.com wrote:
You might not like it, but Gentoo categories have
Hi all,
so I solved my signing question. With a 1024 DSA key you need to add
enable-dsa2
personal-digest-preferences SHA256
to your gpg.conf.
Another question, do we have a rule, how the metadata.xml has to be
indented? Tabs or n spaces?
thanks justin
signature.asc
Description: OpenPGP
On Sun, 26 Jun 2011 00:22:39 +1200
Kent Fredric kentfred...@gmail.com wrote:
Perhaps we need a new way to apply metadata to a whole host of
packages?
Also, categories have extra use for simple convenience of their native
groupings, ie: I've been known to set USE flags/KEYWORDS that apply to
On Sat, Jun 25, 2011 at 1:26 PM, Nikos Chantziaras rea...@arcor.de wrote:
On 06/25/2011 12:35 AM, Michał Górny wrote:
Hello,
git-2.eclass is in the tree for a while now, and there's still awful
lot of packages using old deprecated git.eclass.
I think I remember seeing deprecation warnings
On Sat, Jun 25, 2011 at 6:16 PM, justin j...@gentoo.org wrote:
Another question, do we have a rule, how the metadata.xml has to be
indented? Tabs or n spaces?
There's no rule, but we should follow the same rule as ebuilds —
indentation should be with a tab that's displayed as 4 spaces in
On Sat, Jun 25, 2011 at 08:22, Kent Fredric kentfred...@gmail.com wrote:
I think something else that may be important to consider if one is
eliminating category directories is how we'll replace the utility
currently provided by category/metadata.xml
Some things are simply grossly impractical
Maciej Mrozowski posted on Sat, 25 Jun 2011 13:55:40 +0200 as excerpted:
On Friday 24 of June 2011 09:55:19 Ciaran McCreesh wrote:
So tags are in some way related to categories then?
IMHO the best approach is to forget about categories and:
- make package names unique identifiers (it's
On Saturday 25 of June 2011 17:19:47 Duncan wrote:
Maciej Mrozowski posted on Sat, 25 Jun 2011 13:55:40 +0200 as excerpted:
On Friday 24 of June 2011 09:55:19 Ciaran McCreesh wrote:
So tags are in some way related to categories then?
IMHO the best approach is to forget about categories
On Sat, Jun 25, 2011 at 10:23, Nirbheek Chauhan wrote:
On Sat, Jun 25, 2011 at 6:16 PM, justin wrote:
Another question, do we have a rule, how the metadata.xml has to be
indented? Tabs or n spaces?
There's no rule, but we should follow the same rule as ebuilds —
indentation should be with a
On Sat, 25 Jun 2011, Maciej Mrozowski wrote:
Assuming package names are unique identifiers, tags are not
necessary to be available for ebuild.sh so metadata.xml is the best
place.
But we know that package names are _not_ unique. There are many cases
in the Portage tree where two or even more
On Sat, Jun 25, 2011 at 10:54 PM, Mike Frysinger vap...@gentoo.org wrote:
On Sat, Jun 25, 2011 at 10:23, Nirbheek Chauhan wrote:
On Sat, Jun 25, 2011 at 6:16 PM, justin wrote:
Another question, do we have a rule, how the metadata.xml has to be
indented? Tabs or n spaces?
There's no rule, but
On Saturday 25 of June 2011 19:29:58 Ulrich Mueller wrote:
On Sat, 25 Jun 2011, Maciej Mrozowski wrote:
Assuming package names are unique identifiers, tags are not
necessary to be available for ebuild.sh so metadata.xml is the best
place.
But we know that package names are _not_ unique.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25-06-2011 14:23, Nirbheek Chauhan wrote:
On Sat, Jun 25, 2011 at 6:16 PM, justin j...@gentoo.org wrote:
Another question, do we have a rule, how the metadata.xml has to be
indented? Tabs or n spaces?
There's no rule, but we should follow
On 26 June 2011 05:29, Ulrich Mueller u...@gentoo.org wrote:
On Sat, 25 Jun 2011, Maciej Mrozowski wrote:
Assuming package names are unique identifiers, tags are not
necessary to be available for ebuild.sh so metadata.xml is the best
place.
But we know that package names are _not_ unique.
Hi all,
I've been busy for the past month or two, busy updating some of my
systems. In particular, the Yeeloong I have, hasn't seen attention in a
very long time. Soon as I update one part however, I find some swath of
packages break because of a soname change, anything Python-related stops
On Sat, Jun 25, 2011 at 21:47, Kent Fredric kentfred...@gmail.com wrote:
Package names themselves can be thusly arbitrary , and could be a SHA
sum or something obscure, as long as all internals and dependencies
used the same arbitrary name, things would work as intended.
I mentioned this idea
Stuart Longland posted on Sun, 26 Jun 2011 12:59:05 +1000 as excerpted:
Currently we have three packages that handle this separately:
- revdep-rebuild (handles packages broken by soname changes, etc)
- python-updater (handles Python module rebuilds after upgrading Python)
- perl-cleaner
On 26 June 2011 15:49, Wyatt Epp wyatt@gmail.com wrote:
As for the latter part, the size of a git repo becoming umanageable
over time had not occurred to me, I'm afraid-- would it work to use
shallow clones? Otherwise, the herd-wise division is probably
acceptable. Need to think about
On Sun, Jun 26, 2011 at 4:59 AM, Stuart Longland redhat...@gentoo.org wrote:
- revdep-rebuild (handles packages broken by soname changes, etc)
solved by preserved-libs in portage-2.2
- python-updater (handles Python module rebuilds after upgrading Python)
- perl-cleaner (handles Perl module
On 26 June 2011 17:44, Benedikt Böhm hol...@gentoo.org wrote:
these just exist because python and perl ebuilds are horribly broken.
take a look at RUBY_TARGETS or PHP_TARGETS for an example of how to do
it right. this would also fix all the failures that python and perl
introduce to binary
31 matches
Mail list logo
