On Mon, 26 Apr 2021 12:41:13 +0300
Lassi Kortela <[email protected]> wrote:
> The problem is how to do it. It can be easily brute-forced by listing
> each library and its file name separately. That works well for small
> libraries, but not that well for bit ones. A generic rewriting system
> would handle this problem as well as other, related ones. No-one has
> designed one yet, so we don't have a good grasp of how simple or complex
> it would be; should make a prototype before deciding.
The problem with brute forcing is a browser. With you own computer it's not
an issue to search for a file, but with browser based interpreter (like
try.schmeme.org) everything should be in right place if this is per git repo
it will be easily to fetch the repo and get a file like package.scm from root
directory of a package so see the detail of the package.
Snowball may be problematic when defining package, because I think it's more
for a libraries, if each file is in same directory.
So if you have package with (sort nice) (copy nice) how you will find nice.scm
file or whatever the extension is? On server/computer this maybe not a
problem because traversing the files is fast. But I can't imaging poking in
browser to see if file exists.
--
Jakub T. Jankiewicz, Web Developer
https://jcubic.pl/me
