[Xastir-Dev] Re: New Directory Structure

[Gerry Creager (N5JXS)]

My preference is a 2-directory hack:

System-based maps in /usr/share/xastir/maps with its trickle-down tree 
structure.  Generally, these maps could be system defaults, and a user 
can select them off or on as needed via the pull-down menus.

~/.xastir/maps/... would house my particular local map stash.  They're 
NOT sharable, but if root wants to snag some of my maps and move them to 
/usr/share/xastir/maps, then, they become generally available.

gerry

Jack Twilley wrote:
> WARNING: Unsanitized content follows.
> WARNING: Unsanitized content follows.
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
>>>>>>"Curt" == Curt Mills <Curt> writes:
> 
> 
> Jack> My recommendation is to support multiple, user-definable map
> Jack> directories.
> 
> Jack> ~/.xastir/maps and /usr/share/xastir/maps are good defaults.
> Jack> Someone who mounts their maps on optical media may wish to add
> Jack> their own map directories like /mnt/maps or whatever.
> 
> Curt> As in:
> 
> Curt>     cd .xastir/maps 
> Curt>     ln -s /mnt/maps optical
> 
> Curt> There, problem solved!  
> 
> Actually, no, that's just clutter.
> 
> Curt> User-defineable map directories.  As many as you'd like to
> Curt> define...
> 
> What that produces is another directory layer.  I don't see that as a
> big win.
> 
> Curt> What I'm trying to accomplish with the symlink to
> Curt> /usr/share/xastir/maps:
> 
> Curt> A simple tweak that doesn't require major changes to the map
> Curt> indexing/lookup code, but gives us a unified view of the map
> Curt> directories from within the Map Chooser.
> 
> I can see what you're trying to achieve, I just think the time is
> better spent fixing the map indexing code to handle multiple arbitrary
> directories.
> 
> Curt> You still didn't mention what your preferences were for the
> Curt> default naming (from my last message).
> 
> I was choosing "none of the above", actually, by submitting my
> alternative suggestion.
> 
> We have two directory structures, /usr/share/xastir/maps and
> ~/.xastir/maps.  There are no real requirements for any sort of
> consistency under these directories -- it's up to the software to know
> what to do.  What's the real difference between what you describe with
> the symlink suggestions and this:
> 
> /usr/share/xastir/maps/system/...
> /usr/share/xastir/maps/archer/...
> /usr/share/xastir/maps/jmt/...
> 
> The answer is... nothing.  Why don't we go with this idea?  I'd say
> it's because allowing arbitrary users to write /usr/share/... is bad.
> 
> But back on topic.  I still think fixing the code is a better
> solution.  It is unfortunate that I do not have the time to render the
> point moot by providing an implementation because it would be a really
> fun thing to write.  
> 
> This is part of why I didn't chip in earlier -- goodness knows people
> on the list have seen me chip in on dozens of other issues -- but here
> I am. :-)
> 
> Jack.
> - -- 
> Jack Twilley
> jmt at twilley dot org
> http colon slash slash www dot twilley dot org slash tilde jmt slash
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (FreeBSD)
> 
> iD8DBQE++iXrGPFSfAB/ezgRAseGAKCeHkoqo1nZjCeIUYBclJk74/nb/wCg3FP0
> Ff+ndSmGqthCiCKHX0w5P3s=
> =3nJG
> -----END PGP SIGNATURE-----
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at xastir.org
> https://krypton.hscs.virginia.edu/mailman/listinfo/xastir-dev

-- 
Gerry Creager -- gerry.creager at tamu.edu
Network Engineering -- AATLT, Texas A&M University
Office: 979.458.4020  FAX: 979.847.8578
Cell: 979.229.5301    Pager: 979.228.0173