On Monday 27 August 2007, Bo Ørsted Andresen wrote:
> On Monday 27 August 2007 10:58:02 Alan McKinnon wrote:
> > If I switch to paludis, is it relatively[1] easy to revert back to
> > portage in the event of $UNKNOWN_REASON? (I'm really just looking
> > for a yes or no here)
>
> [SNIP]
>
> > [1] 'r
On Monday 27 August 2007 10:39:25 David Bonnafous wrote:
> After a sync (see below what and how) when I try to re-merge a package
> (same version) and emerge tell me that there is a dependency not
> satified I would like to know where this dependency come from. Because
> this is a "new" dependency,
On Monday 27 August 2007 10:58:02 Alan McKinnon wrote:
> If I switch to paludis, is it relatively[1] easy to revert back to
> portage in the event of $UNKNOWN_REASON? (I'm really just looking for a
> yes or no here)
[SNIP]
> [1] 'relative' is a relative term :-) If it's a similar order of
> magnitu
On Friday 24 August 2007, Bo Ørsted Andresen wrote:
> On Friday 24 August 2007 18:49:38 Alan McKinnon wrote:
> > Sounds like you want to keep the old eclass around inside the
> > overlay and let portage update ${PORTDIR}/eclass/* as it sees fit?
> >
> > I have this setup, I simply created an eclass
Hi,
Bo Ørsted Andresen <[EMAIL PROTECTED]> writes:
> On Friday 24 August 2007 18:24:33 David Bonnafous wrote:
>> I'm working to get a "stable portage overlay" to keep ebuild and files
>> I used to build my system.
>>
>> But even if I keep the ebuild and all the files needed, the command
>> "emerg
On Friday 24 August 2007 18:24:33 David Bonnafous wrote:
> I'm working to get a "stable portage overlay" to keep ebuild and files
> I used to build my system.
>
> But even if I keep the ebuild and all the files needed, the command
> "emerge --sync" introduces some dependencies by modifying eclass.
On Friday 24 August 2007 18:49:38 Alan McKinnon wrote:
> Sounds like you want to keep the old eclass around inside the overlay
> and let portage update ${PORTDIR}/eclass/* as it sees fit?
>
> I have this setup, I simply created an eclass directory in my overlay
> directory, added the ebuild to the
On Friday 24 August 2007, David Bonnafous wrote:
> hi,
>
> I'm working to get a "stable portage overlay" to keep ebuild and
> files I used to build my system.
>
> But even if I keep the ebuild and all the files needed, the command
> "emerge --sync" introduces some dependencies by modifying eclass.
hi,
I'm working to get a "stable portage overlay" to keep ebuild and files
I used to build my system.
But even if I keep the ebuild and all the files needed, the command
"emerge --sync" introduces some dependencies by modifying eclass.
How can I know (localize) this kind of dependencies ?
I fou
9 matches
Mail list logo
