cbagger01

Group: Members
Posts: 4264
Joined: Oct. 2003 |
 |
Posted: May 17 2004,21:45 |
 |
FYI,
When the discussions about custom DSL / DEB configurations started popping up around here, roberts was already well along with developing the mdDSL concept.
It just happened to be a coincidence that the subject of *.deb restoration was brought up right around the time that 0.7 was being OK'ed for release.
But enough about who should get credit for what. The myDSL concept fills a need and gives people the ability to download nicely prebuilt applications that seamlessly integrate with the distribution and require little interaction to get up and running.
I see the *.deb thing as a different situation entirely: Somebody wants to pop their favorite *.debs + dependencies on to a CD and then restore on bootup, but they don't want to turn it into a customized package that is fit for public consumption. Some people are already doing this today.
However, for programs that are useful to a large audience the proper thing to do is to build a *.dsl and then submit it for publishing so that others can easily use this *.dsl program in the future.
|