Within *one* Squeaksource project, it is possible to have different class packages. Is it possible to assign different access right rule to these packages? I only found how to assign globally the access right rule to the whole squeaksource project.
Hilaire
Within *one* Squeaksource project, it is possible to have different class packages. Is it possible to assign different access right rule to these packages? I only found how to assign globally the access right rule to the whole squeaksource project.
Yes, one access right rule per project. It doesn't make much sense to assign access rules to packages as packages are no first-class entities in Squeak or SqueakSource. There are just versions of snapshots of a specific working set. The name and the contents of these versions might change with every commit.
Cheers, Lukas
Lukas Renggli a écrit :
Within *one* Squeaksource project, it is possible to have different class packages. Is it possible to assign different access right rule to these packages? I only found how to assign globally the access right rule to the whole squeaksource project.
Yes, one access right rule per project. It doesn't make much sense to assign access rules to packages as packages are no first-class entities in Squeak or SqueakSource. There are just versions of snapshots of a specific working set. The name and the contents of these versions might change with every commit.
Not sure we talk about the same things. If you look a the 'Latest' link from http://www.squeaksource.com/iFichier.html you will see three different packages eFichier, iFichier and iFichierWeb. It is for these packages I want different access right, not for different versions of the same package.
Hilaire
Yes, one access right rule per project. It doesn't make much sense to assign access rules to packages as packages are no first-class entities in Squeak or SqueakSource. There are just versions of snapshots of a specific working set. The name and the contents of these versions might change with every commit.
Not sure we talk about the same things. If you look a the 'Latest' link from http://www.squeaksource.com/iFichier.html you will see three different packages eFichier, iFichier and iFichierWeb. It is for these packages I want different access right, not for different versions of the same package.
Yes, but from Squeak I can commit eFichier and change the filename in the commit dialog to iFichier for example.
Cheers, Lukas
Lukas Renggli a écrit :
Yes, one access right rule per project. It doesn't make much sense to assign access rules to packages as packages are no first-class entities in Squeak or SqueakSource. There are just versions of snapshots of a specific working set. The name and the contents of these versions might change with every commit.
Not sure we talk about the same things. If you look a the 'Latest' link from http://www.squeaksource.com/iFichier.html you will see three different packages eFichier, iFichier and iFichierWeb. It is for these packages I want different access right, not for different versions of the same package.
Yes, but from Squeak I can commit eFichier and change the filename in the commit dialog to iFichier for example.
Ok, so I guess you mean it is not a good idea to have multiple packages in on project or so?
Hilaire
Ok, so I guess you mean it is not a good idea to have multiple packages in on project or so?
Sure, see the Seaside repository, but managing different security rights won't work.
Cheers, Lukas
beginners@lists.squeakfoundation.org