vs disk space, although Patrick's point of cheap hardware is
>> well taken.
>
> Keep it in your dev space. As I said, the resources argument is only
> available for infra to complain about, and since last I knew from them
> was that it was not a problem right now...
And what if the dev retires/is kicked out?
--
Best Regards
Piotr Jaroszyński
have a dev forum account set up (and I don't
care), but count my vote as "who cares" if there's such an option.
--
Best Regards
Piotr Jaroszyński
;t want it voted on, mark
> it moribund.
As I stated at the last meeting, go ahead and vote on it.
I still think it would be very useful for Gentoo to accept it, I just
kinda lost hope after 2 or 3 times when it was supposed to be voted
upon already.
--
Best Regards
Piotr Jaroszyński
the the geeky *ix way of saying
> "shutup already!"), without actually restricting someone's right to make
> their point... just that they might as well be posting to their private
> diary for the number of others that'll actually read it.
Yeah, that's exactly a thread that belongs to -project and not -dev.
--
Best Regards
Piotr Jaroszyński
On 1 April 2010 15:43, "Paweł Hajdan, Jr." wrote:
> Of course that would mean getting included in
> hardened-ker...@gentoo.org, but I guess it's the easiest part.
Yes, you can do it yourself:
woodpecker ~ $ echo $USER >> /var/mail/alias/misc/hardened-kernel
--
Best Regards
Piotr Jaroszyński
nd you'll be in a foul mood.
I'm pretty sure it says that because there was no way to fail early
before. And failing in the middle of 300 packages upgrade because some
useflags are in conflict wasn't reasonable.
--
Best Regards
Piotr Jaroszyński
ve.
That was treewide cleaning of no* in RESTRICT afair.
--
Best Regards
Piotr Jaroszyński
ell experience at all should conclude with little delay that it
> /could/ be the escaping even if they aren't sure, and a quick suitably
> escaped trial will confirm it.
Where/when does :: need escaping?
--
Best Regards,
Piotr Jaroszyński
PRIOR to the meeting, not during.
4c) is the most important imho.
Also, I think meetings shouldn't be limited to 1 hour. I would move
the limit to at least 2 hours. Even if the process is improved, 1 hour
is just not enough.
--
Best Regards,
Piotr Jaroszyński
2009/6/1 Dawid Węgliński :
> On Monday 01 of June 2009 06:25:06 Jorge Manuel B. S. Vicetto wrote:
>> Hello fellow developers and users.
>>
>
> I nominate:
> peper
Thank you, I accept.
--
Best Regards,
Piotr Jaroszyński
"bad
design" to be an objective argument you need to back it up with
something concrete. For example, could you foresee any actual problems
of the in-filename approach? Cause all I was hearing was "it doesn't
look nice" which now is "oh no, don't expose metadata". The former is
clearly subjective and the latter is already done ($PN-$PV) and
doesn't seem to cause any problems.
--
Best Regards,
Piotr Jaroszyński
2009/5/28 Marijn Schouten (hkBst) :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Piotr Jaroszyński wrote:
>> 2009/5/28 Ulrich Mueller :
>>>>>>>> On Thu, 28 May 2009, Tiziano Müller wrote:
>>>>> ${PORTDIR}/app-misc/foo/foo-1a_live.e
into
> PN and PV. And look at function "pkgsplit" in Portage: It can just
> treat PV as an opaque string.
>
> What would be the advantage to use a hyphen instead of an underscore?
Mainly the thing you observed yourself - foo_live is a bit
inconsistent with current versions.
The case you mention can be avoided with another restriction in PMS.
Buut we might as well go all the way and change the version separator
to -- or something, which would be the most flexible.
--
Best Regards,
Piotr Jaroszyński
2009/5/28 Patrick Lauer :
> On Thursday 28 May 2009 00:12:56 Piotr Jaroszyński wrote:
>> 2009/5/27 Patrick Lauer :
>> > On Wednesday 27 May 2009 22:57:25 Joe Peterson wrote:
>> >> > Gentoo should not repeat the VHS vs Betamax war. For those who do not
>> >
ng the rsync tree, storing all referenced distfiles on
> at least one mirror, then change the rsync path.
> That way all "old" users get the last sane upgrade position (...)
And bugs and security vulnerabilities too. Or do you propose
maintaining multiple trees at the same time? I think one of the main
points of EAPI was to avoid doing exactly that.
--
Best Regards,
Piotr Jaroszyński
2009/5/20 Arfrever Frehtes Taifersar Arahesis :
> 2009-05-17 19:02:02 Piotr Jaroszyński napisał(a):
>> 2009/5/17 Arfrever Frehtes Taifersar Arahesis :
>> > 2009-05-17 18:37:32 Ciaran McCreesh napisał(a):
>> >> On Sun, 17 May 2009 18:20:21 +0200
>> >>
live ebuilds?
You set KEYWORDS="". If you need to do something in profiles with it
you can use profile eapis.
--
Best Regards,
Piotr Jaroszyński
2009/5/17 Robert Buchholz :
> On Sunday 17 May 2009, Piotr Jaroszyński wrote:
>> Hello,
>>
>> I have just updated GLEP 55 [1], hopefully making it a bit clearer.
>>
>> Just FYI, my order of preference of solutions is:
>>
>> 1. EAPI-suffixed ebuilds (o
it breaks first before
posting BS like that? Better yet test it youtself.
[1] - http://dev.gentoo.org/~peper/glep-0055.html#use-newer-bash-features
--
Best Regards,
Piotr Jaroszyński
Just a heads up that I wrote a more detailed description of the
peformance hit that EAPI in the ebuild introduces.
Might come up with some numbers later too.
[1] -
http://dev.gentoo.org/~peper/glep-0055.html#easily-fetchable-eapi-inside-the-ebuild
--
Best Regards,
Piotr Jaroszyński
2009/5/17 Ryan Hill :
> On Sun, 17 May 2009 17:56:06 +0200
> Piotr Jaroszyński wrote:
>
>> Hello,
>>
>> I have just updated GLEP 55 [1], hopefully making it a bit clearer.
>>
>> Just FYI, my order of preference of solutions is:
>>
>> 1. EAPI-suff
; No good, for two reasons.
>>
>> First, this is a global scope change
>
> Why do you think that it is a global scope change?
I have updated the glep, see how it breaks [1].
[1] - http://dev.gentoo.org/~peper/glep-0055.html#use-newer-bash-features
--
Best Regards,
Piotr Jaroszyński
2009/5/17 Arfrever Frehtes Taifersar Arahesis :
> I would like to suggest to include possibility of using of features of
> bash-4.0 (and older versions) in local scope of EAPI="3" ebuilds.
This is glep 55 material. I will update it to reflect that.
--
Best Regards,
Piotr Jaroszyński
he new and
innovative stuff that makes working on Gentoo fun.
[1] - http://dev.gentoo.org/~peper/glep-0055.html
(http://www.gentoo.org/proj/en/glep/glep-0055.html once it synces)
--
Best Regards,
Piotr Jaroszyński
> Using live templates is something more ^^;
For now it looks to me like it is only more work. Could you please
clarify what new functionality they provide?
--
Best Regards,
Piotr Jaroszyński
> The simplest way is to change the syncpoint in the new package manager and
> leave the previous uri with a compatibility repo for the older ones.
So we add a new repo each time a new EAPI comes out? Sounds like a big mess.
--
Best Regards,
Piotr Jaroszyński
���^�X��� ��(��&j)b�b�
while changes breaking the
> sourcing of the ebuild need an increment of X to avoid that pm's not being
> able to even source such an ebuild still can mask it properly (or just
> ignore it).
What's the point of sourcing an ebuild that cannot be used anyway?
--
Best Regards,
Piotr Jaroszyński
ild's EAPI, which is the point here.
--
Best Regards,
Piotr Jaroszyński
ould like to nominate Piotr Jaroszyński (peper).
Thanks, I accept.
--
Best Regards,
Piotr Jaroszyński
2008/6/8 Luca Barbato <[EMAIL PROTECTED]>:
> Piotr Jaroszyński wrote:
>
>> 1. GLEP54
>> 2. GLEP55
>
> None of them got discussion back in -dev, the glep hadn't been changed as
> requested during the unnecessary long discussion in the meeting.
>
> Lo
--
Best Regards,
Piotr Jaroszyński
> peper told me he'd wrap up a few bugs and make a release this week after
> I was about to go touching eselect all over when we know my C/C++ is
> better then my bash.
won't have time till next week ;/ need to finish uni projects and exams.
--
Best Regards,
Piotr Jaroszyński
/dev.gentoo.org/~spb/pms.pdf - section 3.4.3
> http://dev.gentoo.org/~halcy0n/gleps/glep-0054.html
Please, don't use an already assigned GLEP number, it's a bit confusing. Note
that 55 is taken as well.
--
Best Regards,
Piotr Jaroszyński
--
gentoo-dev@lists.gentoo.org mailing list
be somehow tricky... would probably need a
list of already converted packages.
--
Best Regards,
Piotr Jaroszyński
--
gentoo-dev@lists.gentoo.org mailing list
-softmmu if you don't have access to the hw.
Might as well toss a coin or check the phase of the moon...
--
Best Regards,
Piotr Jaroszyński
--
gentoo-dev@lists.gentoo.org mailing list
On Tuesday 01 of January 2008 06:30:01 Mike Frysinger wrote:
> If you have something you'd wish for us to chat about, maybe even
> vote on, let us know ! Simply reply to this e-mail for the whole
> Gentoo dev list to see.
I would like council to discuss GLEP 54 and 55.
--
Best
in both use.desc and use.local.desc, it must be listed once for
each package for which its meaning differs from that described in use.desc."
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
lly the devs running some checks on the whole tree.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ob of the xbuild GLEP to specify what from the ebuild
format applies and what does not.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
it's not clear enough I will look into it.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
org/~peper/glep-0055.txt
--
Best Regards,
Piotr Jaroszyński
GLEP: 55
Title: Use EAPI-suffixed ebuilds (.ebuild-EAPI)
Version: $Revision: $
Last-Modified: $Date: $
Author: Piotr Jaroszyński <[EMAIL PROTECTED]>
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 17-Dec-2007
Post
On Saturday 22 of December 2007 10:50:40 Jan Kundrát wrote:
> Piotr Jaroszyński wrote:
> > The package manger would have to look for ebuilds in the main
> > dir and all the subdirs in case it doesn't have/can't use the cache.
>
> No, it would have to check only for s
d the ietf remark a rather clever reply to the innuendo, making
> the point delicately, while avoiding the loss of face challenge asking
> for an apology presents.
How is it fair that some people do their own research and some ask to be
educated and for the discussion to be delayed?
On Saturday 22 of December 2007 09:09:27 Zhang Le wrote:
> Piotr Jaroszyński wrote:
> > On Thursday 20 of December 2007 19:29:22 Zhang Le wrote:
> >> So please make those people understand, so they can comment usefully.
> >
> > Are we in the elementary school or som
On Saturday 22 of December 2007 02:41:02 Petteri Räty wrote:
> Piotr Jaroszyński kirjoitti:
> > This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds
> > (for example, foo-1.2.3.ebuild-1).
>
> It seems many people don't like the idea of having it in t
On Thursday 20 of December 2007 19:29:22 Zhang Le wrote:
> So please make those people understand, so they can comment usefully.
Are we in the elementary school or something? This is really getting
ridiculous.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
filename approach for its unambiguity.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ouldn't be allowed for obvious
reasons, [A-Za-z0-9+_-] would be fine by me.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Tuesday 18 of December 2007 22:08:52 Thomas de Grenier de Latour wrote:
> extensions for that. A single one is enough: just call files which
> use the rule i've proposed "foo.gbuild" instead of "foo.ebuild",
or .ebuild-ng.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Tuesday 18 of December 2007 20:45:44 Duncan wrote:
> How about when we have a dozen or so EAPIs active, several of which apply
> to a specific ebuild?
Where is this idea of mixing EAPIs coming from? It really doesn't make much
sense.
--
Best Regards,
Piotr Jaroszyński
--
[EMAI
Where he meant a combination of "prefix" and "1" EAPIs, which is prefix
specific.
> Where is documented what characters are allowed in an EAPI string?
Nowhere that I am aware of, but [A-Za-z0-9-_] sounds reasonable to me.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ngs are not limited to digits
> (see ciaranm's message) and may even contain blanks (see grobian's
> message), we would have ebuilds with very strange filenames.
I think you misunderstood grobian's mail, which is "how we do it in prefix"
anyway.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
Hello,
attaching the GLEP.
most current version:
http://dev.gentoo.org/~peper/glep-0055.html
http://dev.gentoo.org/~peper/glep-0055.txt
--
Best Regards,
Piotr Jaroszyński
GLEP: 55
Title: Use EAPI-suffixed ebuilds (.ebuild-EAPI)
Version: $Revision: $
Last-Modified: $Date: $
Author: Piotr
extremely stupid indeed. Let's change it...
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Sunday 09 of December 2007 18:52:22 Petteri Räty wrote:
> "Portage versions prior to 2.1.2.12 (included in 2007.0) doesn't handle
> arbitrary
> version suffixes"
>
> doesn't --> don't
thanks, fixed.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Sunday 09 of December 2007 17:18:08 Josh Sled wrote:
> Piotr Jaroszyński <[EMAIL PROTECTED]> writes:
> > Current html version available here:
> > http://dev.gentoo.org/~peper/glep-0054.html
>
> Until reading the abstract, I thought this was Scheme related.
>
Hello,
Attaching the GLEP source.
Current html version available here:
http://dev.gentoo.org/~peper/glep-0054.html
--
Best Regards,
Piotr Jaroszyński
GLEP: 54
Title: scm package version suffix
Version: $Revision: $
Last-Modified: $Date: $
Author: Piotr Jaroszyński <[EMAIL PROTECTED]>
against,
> try Gentopia's overlay.
mmm fun. I will look into all that during the weekend and at least I know who
to harass :)
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Tuesday 04 of December 2007 02:29:20 Donnie Berkholz wrote:
> evdev input driver
I can take it unless someone else wants it more :)
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Wednesday 14 of November 2007 11:31:13 Torsten Rehn wrote:
> On Wednesday 14 November 2007, Mike Doty wrote:
> > S=${WORKDIR}
>
> Shouldn't ${WORKDIR} be quoted here, too?
No need to quote in assignments.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
e case in first situation.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On 05/11/2007, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> Shouldn't need to create a user twice, and that quoting makes this a bit
> harder to read than it needs to be.
Since which version of portage it's handled correctly?
P.S. my $EDITOR shows quoted strings nicely.
-
ility" flag for paludis and that's also my
candidate for the global one, but better names are welcome.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
s the sources just do
> #include
>
> And this normally will find headers located under /usr/include.
And that's the way to go. When you build with ROOT=/foo DEPEND is installed
into / and only {R,P}DEPEND into /foo.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Sunday 30 of September 2007 02:53:47 Mike Frysinger wrote:
> On Saturday 29 September 2007, Piotr Jaroszyński wrote:
> > On Sunday 30 of September 2007 00:54:29 Torsten Veller wrote:
> > > This fails if tc-getCC returns the path to the compiler
> >
> > It doesn
On Sunday 30 of September 2007 00:54:29 Torsten Veller wrote:
> This fails if tc-getCC returns the path to the compiler
It doesn't, see toolchain-funcs.eclass.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Saturday 29 of September 2007 17:40:35 Markus Dittrich (markusle) wrote:
> - 02 Jul 2007; Piotr Jaroszyński <[EMAIL PROTECTED]> coq-8.0-r1.ebuild,
> + 02 Jul 2007; Piotr JaroszyÅski <[EMAIL PROTECTED]> coq-8.0-r1.ebuild,
>coq-8.0_p3.ebuild:
>(QA) RESTRICT cle
."
>> fi
No reason to check for test in FEATURES, make it die uncodnitionally.
btw. ebuilds shouldn't access FEATURES at all.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Friday 31 of August 2007 12:37:57 Matthias Schwarzott wrote:
> What do you think about adding /etc/udev/rules.d/ to CONFIG_PROTECT_MASK.
That's what I did locally so fine by me.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ying it's breaking something, I just wouldn't except such a
behaviour after reading the docs.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ad my e-mail completly and btw. Paludis is following the same
rules:
A: PDEPEND="B"
B: RDEPEND="A"
Both portage and paludis can end up installing B before A and it seems there
is nothing wrong with it other than that I think it doesn't match the docs.
--
Best Regards,
circular DEPEND <->
PDEPEND can.
Random behaviour occurs when there is a circular RDEPEND <-> PDEPEND, e.g. bug
#186517.
We need to update docs or harass zmedico to force PDEPEND to be pulled as soon
as possible but not before the pkg that pulls it.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ill become)
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
# Piotr Jaroszyński <[EMAIL PROTECTED]> (06 Jul 2007)
# Masked for removal. bug #167379.
x11-themes/gdm-themes
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Sunday 01 of July 2007 01:35:58 Piotr Jaroszyński wrote:
> 2) clean up: we want to do global tree clean up after 1) is resolved, nofoo
> -> foo, rest of the invalid values die.
This is being done NOW.
btw. note that RESTRICT="debug? ( strip )" doesn't make sense.
I am executing 1): RESTRICT="multilib-pkg-force" -> EMULTILIB_PKG="true".
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
n RESTRICT was supposed to mean.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Sunday 01 of July 2007 11:05:24 Marijn Schouten (hkBst) wrote:
> I'm sorry, but I have no idea what `third party values' are.
./multilib.eclass: if hasq multilib-pkg-force ${RESTRICT} ||
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
tree transition.
2) clean up: we want to do global tree clean up after 1) is resolved, nofoo ->
foo, rest of the invalid values die.
3) repoman check: I have contributed a RESTRICT check(10 lines wow:), which
will be in the next portage release. warning for now, error after 2) is done.
quot;
Please be more constructive, join #gentoo-qa and present your suggestions,
ideas and whatnot.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
# Piotr Jaroszyński <[EMAIL PROTECTED]> (24 Jun 2007)
# Masked for removal. bug #165898
x11-drivers/mtxdrivers-pro
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Tuesday 05 of June 2007 23:45:22 Steev Klimaszewski wrote:
> as you have, because apparently, neither of us can follow a simple
> instruction.
I couldn't care less about proctors' instructions after their latest decision.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ernational
forums such as are provided by Gentoo."?
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Wednesday 09 of May 2007 08:04:44 Alec Warner wrote:
> The new layout would be:
I would reserve the breakage for something more useful. Not that I don't like
the idea, just imho such a layout change alone is not worth it.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
opic up.
I have learned about that only after reading the bug you filled. Earlier I
only had known that "portage has support for news items".
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
stalled but not configured
> and the code doesn't seem to have any support for portage at this time
> (checked version was eselect-1.0.9).
Well it's part of Paludis...
Tbh, I expected a little more from portage support for news items than
pointing to eselect module made for pa
On Sunday 06 of May 2007 10:59:01 Marius Mauch wrote:
> It's supposed to be 4 < 4_p == 4_p0 < 4_p1 now.
And it's good as every other _suffix == _suffix0. No reason to make _p
special.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
er what
information paludis' users consider useful enough for a news item.
P.S. If you read carefully enough you find one user's opinion in this
thread...
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Friday 04 of May 2007 23:46:39 Thomas Rösner wrote:
> You mean "Display-If-Installed:
Hello,
Thanks to zmedico we now have support for news items on infra-side and heck
they are ready to use. And we should use them!
Attaching news item for paludis 0.24.
Justification: major config format change.
--
Best Regards,
Piotr Jaroszyński
Title: Changes for Paludis 0.24
Author: Piotr
se of this
discussion is to figure out a compromise between the current state and force
all, because neither of them is good.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
hat we need to figure out is the categories we want to distinguish between in
ebuilds and *then* how to implement that sanely.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ut the
below as things that can be wanted by users/devs and asked whether I missed
something. How we will end up distinguishing them is another story...
> - run all tests
> - run only reasonable tests
> - run only necessary tests
> - don't run tests at all
--
Best Regards,
Piot
nto
groups as current boolean choice seems to be not enough.
> I'd say, let the user decide based on the properties, fex:
It seems to be too early for that. Firstly we should figure out
the "properties" and then we can think how to deliver them for end-users.
--
Best Regards
that list comprehensive?
Please don't post solutions unless we figure out which options we really want
to deliver.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
x27;t matter as long it's 8 digits long)
1.1_rc1 (yuupi version bump and we can use short _rc again)
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
On Tuesday 24 of April 2007 23:20:05 Piotr Jaroszyński wrote:
> foo-0.1_rc2 < foo-0.1_rc000220070313 < foo-0.1_rc3
err. foo-0.1_rc2 < foo-0.1_rc000220070313 < foo-0.1_rc000320070512
What I was trying to say is that once you change to the long versions you must
stay with them.
-
d
> that force portage to update to this version? Wouldn't that prevent
> portage from enforcing update to _rc3 when it's delivered? Of course I
> might be wrong and if this is the case then excuse me for the whole fuss ;)
foo-0.1_rc2 < foo-0.1_rc000220070313 < foo-0.1_r
ally switch to something sane, right?)
and our commit system which must regenerate the Manifest only after commit so
let's kill it.
--
Best Regards,
Piotr Jaroszyński
--
[EMAIL PROTECTED] mailing list
ing project ideas for the next year already
to not look so miserable in comparison with other orgs?
--
Best Regards,
Piotr Jaroszyński
--
gentoo-dev@gentoo.org mailing list
1 - 100 of 138 matches
Mail list logo
