View previous topic :: View next topic |
Author |
Message |
WDef
Joined: 30 Apr 2006 Posts: 20
|
Posted: Sun Aug 27, 2006 6:12 pm Post subject: A naming convention for DSL-N extensions? |
|
|
I'd like to build some extensions specifically for dsl-n, and as such these will/may not work on dsl.
Would it be a good idea perhaps to adopt a simple convention to distinguish these from regular dsl extensions?
Eg placing "-n" before the .dsl, like someapp-n.dsl specifically for dsl-n, as opposed to someapp.dsl for dsl. |
|
Back to top |
|
|
roberts
Joined: 17 Apr 2006 Posts: 320 Location: OC CA USA
|
Posted: Tue Aug 29, 2006 6:55 am Post subject: |
|
|
Much work is underway to try to achieve Debian compatibility.
Now with unionfs, the .dsl type extension does not provide much.
Uci and unc will be the preferred extenions along with .deb
So much work to do, not sure that all existing tested extenions for DSL-N could undergo such a change. Although new ones could certainly use this convention. But then what happens if there is a name change. Not sure. |
|
Back to top |
|
|
WDef
Joined: 30 Apr 2006 Posts: 20
|
Posted: Tue Aug 29, 2006 11:56 am Post subject: |
|
|
Interesting about going for full Debian compatibility. I suppose the low-ram users might still need the occasional .dsl as opposed to a .deb, where a .uci or .unc is not yet available for some reason? No doubt you guys are chewing these things over :=)
This is just to avoid getting someapp.dsl (or uci) and its future dsl-n counterparts mixed up on my harddrive etc (which I will!) in the cases where these are different, have different dependencies in the base system etc, and thus avoid loading a version that perhaps doesn't work properly (eg wants a later libc). The same for someapp.uci, and uncs.
An extension that worked unchanged on both distros already in a single version wouldn't need this by itself, but if a later version got built specifically for dsl-n (eg different dependencies in the base, or a kernel module) then that could get named XXXX-n.uci
In this scheme of things existing extensions for dsl-n wouldn't need to get renamed where these are just unchanged dsl extensions?
BTW I wasn't suggesting a change to the mydsl scripts. Only some name convention, purely to remind the user the extension is intended for dsl-n use (like the *-gtk2.dsl convention which most extension submitters have sensibly adopted for gtk2-factored extensions on dsl).
Perhaps it wouldn't matter much if dsl-n changed its name in this regard - the *-n.[ext] (or whatever got chosen) flag could remain so long as its meaning got understood. |
|
Back to top |
|
|
|