Re: [gentoo-portage-dev] The merge of emerde with emerge

[Luke-Jr]

On Wednesday 01 December 2004 8:51 pm, Alpt wrote:
> On Wed, Dec 01, 2004 at 07:22:56PM +0000, Luke-Jr wrote  :
> > On Wednesday 01 December 2004 5:55 pm, Alpt wrote:
> > > Emerde is born on Septmber 2003. It is a port of the portage for
> > > slackware or generic distro. ( http://emerde.freaknet.org )
> >
> > This doesn't make sense to me... Portage is universal enough to work on
> any ~> other common Linux system...
>
> okey, install it in slackware then and use it. let me see please.

There's no purpose. If you want to use Portage, you might as well use Gentoo. 
I see no reason why it shouldn't work, though.

>
> > > In the while I've added various handy features.
> > > These are the additional features added in emerde:
> > > tgz support: A  tgzfile must be a Slackware pkg. Emerde will resolve
> > >  the tgz's dependences and will install it.
> ~>
> ~> Shouldn't be part of Portage. Portage handles ebuilds, not Slackware
> packages.
>
> It is to let emerde live peacefull in Slackware.

Inject stuff. I don't see RPM installing DEB, tgz, or ebuilds.

> > > maketgz: Emerde will build  Slackware's  tgz packages for all ebuilds
> >
> > A better idea would be to convert GRPs to Slackware tgz
>
> Slackware compatibility dude.

You're saying Portage isn't Slackware compatible because you define Slackware 
to be non-Portage.

>
> > > Compilation resume:
> > >   Emerde resumes an interrupted or aborted compilation without rebuild
> > >   the pkg and restart the compilation.
> >
> > Portage already does this for me.
>
> no, if halt the compilation and the next time ./configure will be runned
> so you'll start the compilation again.

Nope... In fact, I can change my USE and it will still output the same stuff 
since it doesn't recompile anything. A bug, but it doesn't annoy me enough.

> > > initd-cfg: /etc/init.d editor.
> >
> > Doesn't belong in a package manager.
>
> you are managing the init.d files of the packages installed with the
> package manager

Shall we include editors for all the other possible configuration files 
Portage packages install too?

>
> ~> Portage is already distro-independent... The only distros to have
> considered ~> using it (Zynot and Utopios) both determined that it would be
> better to write ~> a better package manager based on the ideas.
>
> Install it in the other distro then. Did you considered for example
> baselayout?

Inject baselayout.

On Wednesday 01 December 2004 9:14 pm, Colin Kingsley wrote:
> > Portage is already distro-independent... The only distros to have
> > considered using it (Zynot and Utopios) both determined that it would be
> > better to write a better package manager based on the ideas.
>
> hmmm.... So portage is universal enough, yet other distro's have
> decided to write their own package manager?

It'll work on systems w/o any changes, but that doesn't mean it works well. 
There are numerous flaws in the design of Portage that cannot simply be 
"fixed."

> > > Compilation resume:
> > >   Emerde resumes an interrupted or aborted compilation without rebuild
> > >   the pkg and restart the compilation.
> >
> > Portage already does this for me.
>
> No it doesn't. He means that a compile would be resumed from where
> ever it left off, as if you were doing ./configure && make && make
> install  style compilation. Currently, portage will pick up from the
> beginning of the package that was being compiled when it died.

Continues from where it left off for me. Possibly related to keeptemp or 
keepwork.


> >> por2pkg: por2pkg converts entries in the portage's db to Slack's db
> >> entries. pkg2por: pkg2por converts entries in the Slack's db to portage's
> >> db entries. pordbcheck: Checks if the programs listed in the portage's db
> >> are really installed.
>
> >Doesn't belong in a package manager.
>
> No? Then where would a tool to manipulate _package_ databases belong?

Same place as app-arch/alien
-- 
Luke-Jr
Developer, Utopios
http://utopios.org/

--
gentoo-portage-dev@g.o mailing list