[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: YaST2 for Debian (aka nYaST)

> > Easier no, because it will require touching of many C++ sources, part of
> > the core, instead of patching only the autoconf/automake stuff, but
> > better, because some time in the future it will be necessary - we can't
> > lie the system at all - I don't think we could build the whole system
> > (with modules) just with recompilation and some hacks. As you said in
> > long term we should start a *new* project - I mean this will not be port
> I'm not happy with this *new* project thing. 
Me too, because as I said if we go to this way - the task growing 10
times and nobody can say when we would finish :-/

> But if you say, there's no other 
> way, I believe you because you know a lot more about the code. But I prefer a 
> close relationship with SuSE/Novell/YaST2. 
Me too, don't misunderstand me - if SuSe/Novell/YaST guys say yes, lets
make some work together - I'll be really happy :-)))

> I'd like to avoid a fork. See my 
> other mail for some reasons.
Of course you are right, I just say, that without strong backup from SuSe/Novell we will 
loose much more time trying to lie the system, that the rpm (and other
specific SuSe stuff) is ok for Debian.. So, We should think twice before
start the "road map" of the project. In summarise let me share my
1. We have strong (technical) support from SuSe/Novell about YaST
2. We have experienced dpkg internals Debian developer on our side
If we complete this requirements, I think it wouldn't be necessary to
fork the YaST.. 

> Think as well about security things where we could profit from the upstream 
> authors if our yast is close to theirs.
At least.. there is so much similar examples.. I agree with you..

> > of YaST for Debian, it will be new system based of YaST... More and more
> > every day I understand how big is such task.. In this meaning, we will
> > need somebody really good with dpkg developing.. I would ask in the
> > devel list if somebody would like to participate.. Otherwise I'll need
> Ok, this is something I could do. Do you think of any specific person?
I have an idea about some persons, but it better to ask them all because 
personal messages is not so hmmmm popular, let say, in the mailing list, I
mean I'm sure that there is enough experienced developers in the devel
list, so somebody will participate (I hope) :-))))

> > at least 3-4 months to dig into dpkg internals (I'm interested in this
> > part of this a long time ago, but hadn't enough free time..)
> >
> > > Is it worth to spend the time with rpm in your opinion?
> >
> > Yes and no.. For testing what will happens after successfully compilation
> > maybe and patching only the simplest scripts will give us quick results,
> > but in a long term rpm should be removed (in my opinion)..
> Ok, do have a time estimation for the rpm stuff?
Not yet :-/

> > Excellent, I have no experience with configuring GForge (I hear only
> > rumours how hard is to set such system), but I guess setting just a project
> Oh, that sounds great. My skills are so poor and it's so hard. But hey, I try 
> and learn.
good luck :-)
> > on it, is easier, so go on make a project and I will upload there the
> > pathces that I made..
> I asked for an alioth project and I am now waiting for the answer of the 
> alioth people.

> > > PS: Did you get in contact with some people of Novell? See my other mail.
> >
> > Before 4-5 months.. Without result.. :-/
> Ok, so I try to get in contact with them.
Thanks :-)


Rumen Krasstev - Object Builder Software Bulgaria
Sofia, 113 Tzarigradsko Shose, phone: +359 2 974 33 16
web: http://www.obs.bg, email: rkrastev@obs.bg, icq: 35447386
###I'm using only free or/and open source software### 
Share the freedom - "Free Software Association - Bulgaria" http://www.fsa-bg.org

Reply to: