| 1 |
On Wed, 1 Dec 2004 19:22:56 +0000, Luke-Jr <luke-jr@×××××××.org> wrote: |
| 2 |
> On Wednesday 01 December 2004 5:55 pm, Alpt wrote: |
| 3 |
> > For those who don't know the story: |
| 4 |
> > Emerde is born on Septmber 2003. It is a port of the portage for |
| 5 |
> > slackware or generic distro. ( http://emerde.freaknet.org ) |
| 6 |
> |
| 7 |
> This doesn't make sense to me... Portage is universal enough to work on any |
| 8 |
> other common Linux system... |
| 9 |
|
| 10 |
[..snip..] |
| 11 |
|
| 12 |
> Portage is already distro-independent... The only distros to have considered |
| 13 |
> using it (Zynot and Utopios) both determined that it would be better to write |
| 14 |
> a better package manager based on the ideas. |
| 15 |
|
| 16 |
hmmm.... So portage is universal enough, yet other distro's have |
| 17 |
decided to write their own package manager? One of which, you are a |
| 18 |
developer for (according to your sig)? Maybe its worth listening to |
| 19 |
this guy, or at least not shooting him down without a second thought. |
| 20 |
Especially since he actually has a patch and some nice things to say, |
| 21 |
instead of the standard useless complaints. |
| 22 |
|
| 23 |
> > In the while I've added various handy features. |
| 24 |
> > These are the additional features added in emerde: |
| 25 |
> > tgz support: A tgzfile must be a Slackware pkg. Emerde will resolve the |
| 26 |
> > tgz's dependences and will install it. |
| 27 |
> |
| 28 |
> Shouldn't be part of Portage. Portage handles ebuilds, not Slackware packages. |
| 29 |
|
| 30 |
I was under the impression that support for third party packages was |
| 31 |
in the works for portage? If so, dep resolution for a .tgz would be |
| 32 |
quite handy. Am I wrong? |
| 33 |
|
| 34 |
> |
| 35 |
> > pfile: Emerde will apply the specified action to all the packages listed |
| 36 |
> > in the pfile |
| 37 |
> |
| 38 |
> emerge $(cat pfile) |
| 39 |
|
| 40 |
Stop being pedantic. Clearly, the point of this function is to make it |
| 41 |
easy to perform actions on large groups of packages without shell |
| 42 |
magic. |
| 43 |
|
| 44 |
> > maketgz: Emerde will build Slackware's tgz packages for all ebuilds |
| 45 |
> |
| 46 |
> A better idea would be to convert GRPs to Slackware tgz |
| 47 |
|
| 48 |
How would this be any different? or better? I'd say the ability to |
| 49 |
create, as well as install third party packages is kind of nifty. Why |
| 50 |
would it be better to convert a Gentoo package instead of natively |
| 51 |
creating the .tgz? |
| 52 |
|
| 53 |
> > Compilation resume: |
| 54 |
> > Emerde resumes an interrupted or aborted compilation without rebuild |
| 55 |
> > the pkg and restart the compilation. |
| 56 |
> |
| 57 |
> Portage already does this for me. |
| 58 |
|
| 59 |
No it doesn't. He means that a compile would be resumed from where |
| 60 |
ever it left off, as if you were doing ./configure && make && make |
| 61 |
install style compilation. Currently, portage will pick up from the |
| 62 |
beginning of the package that was being compiled when it died. |
| 63 |
|
| 64 |
>> por2pkg: por2pkg converts entries in the portage's db to Slack's db |
| 65 |
>> entries. pkg2por: pkg2por converts entries in the Slack's db to portage's |
| 66 |
>> db entries. pordbcheck: Checks if the programs listed in the portage's db |
| 67 |
>> are really installed. |
| 68 |
|
| 69 |
>Doesn't belong in a package manager. |
| 70 |
|
| 71 |
No? Then where would a tool to manipulate _package_ databases belong? |
| 72 |
|
| 73 |
|
| 74 |
Colin |
| 75 |
|
| 76 |
-- |
| 77 |
gentoo-portage-dev@g.o mailing list |
Archives