Open nickl- opened 12 years ago
LOL, there is so much that I have to catch up. What about aero-recycler, or something which has one of its functionalities?
I like the "aero-recycler" idea. "aero-as" would fit our domain name (I've bought aero.as), but is kinda meanless. We can still use just "aero" in the command line right?
And I have lots of ideas for the ascii planes still so aero it should remain. recycler is cool as describing the purpose bit no matter which way you look at recyclers it remains garbage disposal, you know....
Anyway there are other aero's too something happening withe an aero.io I think it was up and coming or came and gone one of those?
Is it installing? Did I get all the deps? What do you think about the planes? =)
@alganet wrote:
still use just "aero" in the command line right? Alas the clashing package aero 0.3.6a unfortunately does just that, overwrites our aero if having the same name was not bad enough
I would like to keep the name aero regardless of the package name or executable, reason being that I've grown rather fond of the planes.
We should ideally stay with a short name, the most common practice seems to be between 3 - 5 chars. It does not make much sense if the recycler/wrapper/facilitator/combiner's command is 3 times longer than those it is trying to facilitate, or am I being silly? (I don't like recycler either, a recycler reuses waste. Are we trying to say the PMs are rubbish?)
npm apt yum brew pear pecl pyrus pip gem
which is whey aero was perfect play on aeroplane aeri aery aere aerp aerop plane apln sky
Package manager - it's not anpm - aero is no a package manager apm - aero is still not a package manager pmin - pm it's not mpa - aero is not a package manager written backwards pma - aero is not a package manager a behind pm - aero is not a package manager silent a pam - aero is not a package manager sandwich
I started out with the anpm
idea now I like apm
or pam
the latter would surely spur the question why pam?
Who's Pam?
ex-girlfriend perhaps? =)
now it also has a really funny story to it.
Loved plane. Is name assembling. But, sounds unclear :/ Just installed aero, why should I run
$ plane --help
apm is the most sober. While sky becomes a valid suggestion, air could be too, not?
We could change the entire project's name to something else as well =) Why not?
(as long as we keep some relation to planes =P)
I am still not sure what the impact is, I guess we'll find out when we want to go on pypy perhaps keeping the name aero is fine as a command stil.
It's a pleasure to type on dvorak =)
Has anyone tested alpha 3 yet? Should we add more commands first (update, delete/remove) before moving to stable trea?
I'm using it daily and it seems to be behaving for most of what I ask of it. Thoughts?
@oliveiraev apm is the most sober.
Damn and I was liking that, no way we could use it now. I guess pam it is then? =)
Pam reads nice and sounds nice, +1!
(should we use the same meritocracy-based voting as we do on Respect for Aeronautics and Hidro as well?)
+1 pam - aero is not a package manager sandwich
@Aeronautics/aero see https://github.com/Respect/project-info/issues/13 for a summary of what @alganet is referring to.
@alganet @jaysonsantos it appears we have a name collision as there is another aero package registered on pypi.
What do you say?