cssed
Posted: 9. Jun 2011, 17:43
I've read in slackware that just getting the source code for an application , & doing ./configure ,
make , make install isn't the best way to install a package for reasons which are slowly being assimilated by what's left of my grey matter.
I'm after cssed which is a nice style sheet editor, I have had a look using Gslapt, sourcery
and looked at slackbulds.org ; none of them have it unless I’m missing something.
I can can get the source code from http://cssed.sourceforge.net/ ; now being realistic and taking into account I’m fairly new to the idea of builds , am no spring chicken , & have a user name which suggests I’m not related to Einstein ,how easy would it be to construct
./package
|-- README
|-- package.info
|-- package.SlackBuild
|-- package.desktop
|-- package.png
|-- slack-desc
Well you know the old adage build it for them , and they will be OK for a while, but teach em how to build it themselves will last them a life time
make , make install isn't the best way to install a package for reasons which are slowly being assimilated by what's left of my grey matter.
I'm after cssed which is a nice style sheet editor, I have had a look using Gslapt, sourcery
and looked at slackbulds.org ; none of them have it unless I’m missing something.
I can can get the source code from http://cssed.sourceforge.net/ ; now being realistic and taking into account I’m fairly new to the idea of builds , am no spring chicken , & have a user name which suggests I’m not related to Einstein ,how easy would it be to construct
./package
|-- README
|-- package.info
|-- package.SlackBuild
|-- package.desktop
|-- package.png
|-- slack-desc
Well you know the old adage build it for them , and they will be OK for a while, but teach em how to build it themselves will last them a life time