Re: [Slacktools-dev] The use of mailing

[João Ferreira]

On Fri, 4 Jul 2003 21:55:18 +0100
Paulo Abrantes <address@hidden> wrote:


> 
>  So mainly what you want do is an apt-get fork? The problem I see here in 
> that is the 
> how can you know if the user is a debian or slackware user, in the server. 
> The only 
> way I'm seeing here is doing some tweaking in the apt "procotol". So the 
> server code 
> would also have to be changed. Which I think apt folks wouldn't really like. 
> If you are seeing another way to solve this problem, or if I'm not quite 
> following the 
> apt protocol, please enlight me :)
> 
> 

Well, the first idea i had was to create just a new package tool for slack with 
dependencies, etc...
But after using apt from debian (which I suggest to everyone), I think there is 
nothing better! The question 
is: how can we use apt code and servers in our project?

Apt for RedHat, for instance, uses different servers and in those servers there 
are RPMs. This is not bad, BUT
not good. We have the possibility of making .debs available in slackware... but 
I think it's not a good idea..

Well, basically, what I'd like to do is to create a simple way to install 
software and keep track of it... how? I have no idea... :)
But in the end, it just have to follow the KISS ideology :)



> >  
> >  * Easy way to create, install, uninstall, and keep track of packages
>    
>    Well that's the easy part. Mainly the core of this tools will be the 
> sync'ing with servers, retrieving the packages and their deps, that's
> the part we have to think and discuss, the localhost part is (probably)
> just a bunch of perl scripts;)
> 
> 

I agree :) Perl or Python [/me grins]

:)


Regards,
João